Can someone let me know why my account was removed here at eblah?

Member # 7093

No clue. I don't have the proper access to tell why that happened. Maybe another admin can clear that up.

No idea... Martin also had problems here this week

I see other account had issues as well. So it seems ot be a site issue.  Please let me know when its resolved, I have unopened PMs I need to read

Thanks everyone.

-ps this happened on my site too recently.

Can an admin/mod please look into this?

A post has been made in the admin section of this site to the issue and problem. Have now to wait for Justin to feed back and comment.. Martin has also lost his "credentials"

I would also like to point out that this problem does demonstrate that the negative comments about hosting compainies like Heart Internet are now now dead in the water. And I look forward to more constructive comments with regards to hosting companies.

Nat, pack it in with the Heart Internet comments, just because you buy their reseller package doesn't mean everyone else will have the same experience you've had.
Please leave people to offer advice and do with it as they please.

Quoted Text

Nat, pack it in with the Heart Internet comments

Only when you stop blaming them for problems. You will notice that our much respected Martin, has now lost his account, and that this forum is not hosted with Heart... Hence it proves that there is a problem with the script and not the hosting company.

So please do read again what I wrote

Quoted Text

I would also like to point out that this problem does demonstrate that the negative comments about hosting compainies like Heart Internet are now now dead in the water. And I look forward to more constructive comments with regards to hosting companies.

Thank you.

Quoted Text

Only when you stop blaming them for problems.

No, Nat. You need to understand that people are free to comment how ever they wish. That includes passing on feedback on companies they've used before. You need respect that and stop fl aming me for it.

Sorry, but I stand by what I say... I made no mention of you, but if the cap fits and all of that...

Thanks for fixing my account.

I too had this happen to my forum 3 weeks ago.......

This is a similar situation to that we are experiencing on our forum

Members booted out of accounts or unable to log in

Accounts deleted

Pm's down (at least once a day sometimes more)

I hope Justin manages to get this fixed as it now seems to be admitted in some quarters to being a software issue - we are losing members left, right and Center over this.

This seemed to happen with my forum recently as well. I looked at the member data files on my server and they showed as zero byte files. I will soon be converting from a E-Blah flat-file to E-Blah SQL though so I won't have problems with member files becoming empty. I understand that E-Blah SQL is technically still under beta, but I've been working on writing my MS SQL driver for E-Blah SQL and have learned a lot about how it works. I may even be able to help fix some of the bugs in E-Blah SQL to make it more stable eventually.

As is thoroughly explained in the other thread, there are several ways this can happen.  I generally don't blame any hosting providers though some do have more problems than others.

The problem is that there's some reason a file is opened to be written to but it can't and fails.  All .dat file writes are centralized into one function within E-Blah (SaveMemberID, in Load.pl).  The most probable (and usually reasons) why this fails is because server space is low, the E-Blah process is killed (during a write operation), or file locking is not supported by the file system.

That all said, there is ONE possibility I just found that could cause this to happen, though it shouldn't happen because of file locking.  If anyone wants to test it do the following in Load.pl, search for:

Code if($failsafe != 1) { return(); }

Add this after:

Code $size = @printuser; if($size <= 0) { return(); }

Search for:

Code my($iddata,$item,$itemvalue,@printuser,$hasdat,$failsafe, $size);

Replace with:

Code my($iddata,$item,$itemvalue,@printuser,$hasdat,$failsafe);

All this does is make absolutely certain that there is, indeed, at least SOME data being written to the member .dat file.

I have put in a check on the E-Blah server and will get an e-mail if this problem ever occurs.  If I get an e-mail, I will release a new version promptly.