Page Index Toggle Pages: [1] 2 
Topic Tools
Hot Topic (More than 10 Replies) After migration to new server, threads no longer marked as read (Read 2,112 times)
Dandello
YaBB Administrator
YaBB Next Team
Operations Team
Beta Testers
Support Team
*****
Offline



Posts: 2,125
Location: Earth

YaBB 2.6.0
Re: After migration to new server, threads no longer marked as read
Reply #21 - Jan 18th, 2013 at 2:23pm
Post Tools
Glad it's sorted out.

(I did find one complaint online where Perl14 miswrote things due to some under-reported deprecated code. But if that were the case, then it would still be happening.)

Chalk it up to "it's a mystery"  Roll Eyes
  

If you only have one solution to a problem you're not trying hard enough!
Back to top
WWW  
IP Logged
 
pyragony
Language Team
YaBB Next Team
Beta Testers
****
Offline



Posts: 212
Location: 31855 Aerzen

None
Re: After migration to new server, threads no longer marked as read
Reply #20 - Jan 18th, 2013 at 9:08am
Post Tools
  

Back to top
 
IP Logged
 
xnoddyx
Support Team
Documentation Team
YaBB Moderators
YaBB Next Team
Beta Testers
****
Offline



Posts: 1,584
Location: UK:Scotland/livingston

None
Re: After migration to new server, threads no longer marked as read
Reply #19 - Jan 18th, 2013 at 8:59am
Post Tools
Frank W wrote on Jan 18th, 2013 at 7:41am:
Ok you can consider this case closed. I still don't know what was wrong initially, I just testwise did the same migration to another server with the same settings and perl-version. There was no Problem at all so I assumed the migration must have gone wrong. I therefore did the migration again to the server, this time manually not using the plesk migration manager and now the forum works fine. Thank you all for your help and effort. I am sorry I caused you trouble. As I said I still dont know what went wrong and it is pretty odd, that the only problem that occured was this read/unread problem.Thanks againyours Frank


xnoddyx wrote on Jan 17th, 2013 at 4:05pm:
a server migration can make some problems if user permissions are not setup correctly on the new server

user permissions owner permissions good to see that you are up and running agen  Wink
  

YaBB install help video
1. what yabb forum are you running and the url
2. describe in as much detail as you can what happens and also post screenshots if you can
3. please be patient we live in different time zones and have other commitments but we will help you
as bill and ted say (Be excellent to each other)
Back to top
IP Logged
 
Frank W
YaBB Newcomer
*
Offline



Posts: 26
Re: After migration to new server, threads no longer marked as read
Reply #18 - Jan 18th, 2013 at 7:41am
Post Tools
Ok you can consider this case closed. I still don't know what was wrong initially, I just testwise did the same migration to another server with the same settings and perl-version. There was no Problem at all so I assumed the migration must have gone wrong. I therefore did the migration again to the server, this time manually not using the plesk migration manager and now the forum works fine. Thank you all for your help and effort. I am sorry I caused you trouble. As I said I still dont know what went wrong and it is pretty odd, that the only problem that occured was this read/unread problem.

Thanks again

yours Frank
  
Back to top
 
IP Logged
 
Dandello
YaBB Administrator
YaBB Next Team
Operations Team
Beta Testers
Support Team
*****
Offline



Posts: 2,125
Location: Earth

YaBB 2.6.0
Re: After migration to new server, threads no longer marked as read
Reply #17 - Jan 18th, 2013 at 6:40am
Post Tools
I'm beginning to wonder if the issue has to do with some quirk with Perl 14 and YaBB 2.4. - That the old messages show as read makes sense - the program just reads the current time and compares it to the age of the post. There's no writing to files. I'm going to be away for the weekend, but I'll install ActivePerl 14 as soon as I can and check out why the .log files are not being properly written to. And that's happening in a sub routine called dumplog. (There's also one called undumplog that handles removing the information when something is marked unread.)

All the javascripts do is turn over the graphics.

You can PM the login info.

« Last Edit: Jan 18th, 2013 at 6:41am by Dandello »  

If you only have one solution to a problem you're not trying hard enough!
Back to top
WWW  
IP Logged
 
Frank W
YaBB Newcomer
*
Offline



Posts: 26
Re: After migration to new server, threads no longer marked as read
Reply #16 - Jan 18th, 2013 at 6:14am
Post Tools
There is another thing, that might help. I just checked: All Threads older than Oktober 18th are marked as read, all newer threads are marked as unread. That is aproximately the 90 days setting you were talking about earlier.
  
Back to top
 
IP Logged
 
Frank W
YaBB Newcomer
*
Offline



Posts: 26
Re: After migration to new server, threads no longer marked as read
Reply #15 - Jan 18th, 2013 at 6:07am
Post Tools
There are a dozen threads showing up as read and the times make sense. I already checked the server clock and it is set correctly. I also did a new post, and the time of the post was correct. If it helps you, I can send you the link of the forum together with some demo login data.

Yours Frank
  
Back to top
 
IP Logged
 
Dandello
YaBB Administrator
YaBB Next Team
Operations Team
Beta Testers
Support Team
*****
Offline



Posts: 2,125
Location: Earth

YaBB 2.6.0
Re: After migration to new server, threads no longer marked as read
Reply #14 - Jan 18th, 2013 at 5:47am
Post Tools
There is one time where I've actually seen this happen - when the post time stamp was in the future (as in the server time was way off or I had hand edited the time  on a post to make it appear as though it had been posted in the future.).  Are there any posts that are showing up as read? How old are they?  Do the times on the actual Posts make sense?

Also be advised there may be issues with running YaBB 2.4 on Perl 14. See: http://www.yabbforum.com/community/YaBB.pl?num=1344021417
« Last Edit: Jan 18th, 2013 at 5:58am by Dandello »  

If you only have one solution to a problem you're not trying hard enough!
Back to top
WWW  
IP Logged
 
Frank W
YaBB Newcomer
*
Offline



Posts: 26
Re: After migration to new server, threads no longer marked as read
Reply #13 - Jan 18th, 2013 at 5:14am
Post Tools
The perl version on the old server where everything was running well was 5.8.8. On the new server the perl version is 5.14.2. I also checked the $max_log_days_old it is set to 90
  
Back to top
 
IP Logged
 
Dandello
YaBB Administrator
YaBB Next Team
Operations Team
Beta Testers
Support Team
*****
Offline



Posts: 2,125
Location: Earth

YaBB 2.6.0
Re: After migration to new server, threads no longer marked as read
Reply #12 - Jan 18th, 2013 at 3:57am
Post Tools
Actually, I did some experimenting - setting $max_log_days_old to 0 makes it so no boards are ever marked as unread because they're over the age limit.

What it seems to look like is the log isn't being properly written to. Instead of keeping the old info in the file, it's erasing everything and appending the last entry. Has the version of Perl changed?
  

If you only have one solution to a problem you're not trying hard enough!
Back to top
WWW  
IP Logged
 
Dandello
YaBB Administrator
YaBB Next Team
Operations Team
Beta Testers
Support Team
*****
Offline



Posts: 2,125
Location: Earth

YaBB 2.6.0
Re: After migration to new server, threads no longer marked as read
Reply #11 - Jan 17th, 2013 at 9:46pm
Post Tools
The name refers to an entire board - so that's okay.
What isn't okay is the fact that instead of the file being added on to, all the data's being replaced. Which means (most likely) that the subroutine 'dumplog' isn't getting the proper time information in so it can determine which timestamps it should not remove. It's only supposed to remove items that are too old or have been marked via javascript as unread. (and the determination if something's too old comes from DateTime.pl.)

There's a variable called $max_log_days_old that may have gotten set to 0 or nothing. It should be in Advanced Settings -> Advanced.

Make sure it's set to a reasonable number like 60 or 90.
« Last Edit: Jan 17th, 2013 at 9:48pm by Dandello »  

If you only have one solution to a problem you're not trying hard enough!
Back to top
WWW  
IP Logged
 
Frank W
YaBB Newcomer
*
Offline



Posts: 26
Re: After migration to new server, threads no longer marked as read
Reply #10 - Jan 17th, 2013 at 8:18pm
Post Tools
As said above, I even deleted the .log file of a user, and yabb created a new one but the threads are still unread no matter what I do, and all the users have the same unread threads, what is odd the most. The newly created files consist of e.g. small|1358449712 which seems odd, cause I didn't expect other things than numbers in there. Is that correct?

Edit: I discovered something new, the .log file is not growing, it is always only 1 line big, but this line changes when I visit a thread. Is this of any help?

Yours, Frank
« Last Edit: Jan 17th, 2013 at 8:35pm by Frank W »  
Back to top
 
IP Logged
 
Dandello
YaBB Administrator
YaBB Next Team
Operations Team
Beta Testers
Support Team
*****
Offline



Posts: 2,125
Location: Earth

YaBB 2.6.0
Re: After migration to new server, threads no longer marked as read
Reply #9 - Jan 17th, 2013 at 7:52pm
Post Tools
Since you were able to add a new member, the CHMOD for the folder is correct, but are the CHMODs for the *.log files correct?

When you open a *.log file, what's inside it? (There should be lists of things like: '1345832898|1345992783' - the first is the thread and the second number is a Perl time stamp.

The subroutine that writes to the 'mark as read' doesn't throw an error if it can't do its job, so there won't be anything in any of the error logs.
« Last Edit: Jan 17th, 2013 at 8:01pm by Dandello »  

If you only have one solution to a problem you're not trying hard enough!
Back to top
WWW  
IP Logged
 
Frank W
YaBB Newcomer
*
Offline



Posts: 26
Re: After migration to new server, threads no longer marked as read
Reply #8 - Jan 17th, 2013 at 6:25pm
Post Tools
Quote:
a server migration can make some problems if user permissions are not setup correctly on the new server do you have access to the server logs?


I have access to the logs but the apache error log shows nothing yabb related.

Quote:


These files all have the right permissions and are also created newly if I access a thread. So still no clue Sad

Edit 1: I just discovered something even more funny. For every user, the same threads are unread. Seems like yabb is using the same logfile for all users. Thats odd. Any idea?

Edit 2: I just tested it. I deleted the .log file of a user. Afterwards the same threads as before were marked as unread, nothing changed. I then visites an unread thread and a new user.log file was created but the thread was still unread anyway.
« Last Edit: Jan 17th, 2013 at 7:28pm by Frank W »  
Back to top
 
IP Logged
 
xnoddyx
Support Team
Documentation Team
YaBB Moderators
YaBB Next Team
Beta Testers
****
Offline



Posts: 1,584
Location: UK:Scotland/livingston

None
Re: After migration to new server, threads no longer marked as read
Reply #7 - Jan 17th, 2013 at 4:05pm
Post Tools
Frank W wrote on Jan 17th, 2013 at 3:12pm:
The .js files are there, it's a one to one copy done by the migration manager of the plesk administration interface. As far as I have seen and checked, all chmods are right, but I will check em again.

a server migration can make some problems if user permissions are not setup correctly on the new server do you have access to the server logs?

Frank W wrote on Jan 17th, 2013 at 3:12pm:
In which files yabb saves the read/unread state of certain threads for a user?

see http://www.yabbforum.com/codex/YaBB.pl?num=1224094402 top of page username.log
  

YaBB install help video
1. what yabb forum are you running and the url
2. describe in as much detail as you can what happens and also post screenshots if you can
3. please be patient we live in different time zones and have other commitments but we will help you
as bill and ted say (Be excellent to each other)
Back to top
IP Logged
 
Page Index Toggle Pages: [1] 2 
Topic Tools
 
  « Board Index ‹ Board  ^Top