Server Downtime - May 13th-16th, 2025

[vdeane]

Country flags are gone too, though I think a lot of us stopped using them by this point.  Also, changing your profile details apparently nukes your avatar, with no way to get it back unless you have external hosting.

EDIT: Managed to find it in the gallery listing.  Also, it's hilarious that there's still a spot for Skype usernames with Skype no longer being a thing.

[cahwyguy]

Just a note to say THANK YOU to Alex for all his hard work on the forum. The Pacific Southwest forum is one I depend upon as a primary source of information for my pages, as well as a primary place to promote when I do California Highway Headline posts, posts of updates to my pages, and posts about the California Highways podcast. It has always served as a relatively high quality source of information.

I know the incredible amount of work that goes into maintain all of this, and I just want to let @Alex know that I appreciate it.

The one suggestion I might make is to create a read-only, non-forum page off AARoads (e.g. .../forumstatus.html) that just provides a status update on the forum for downtimes like this. The AARoads FB page, which would be a logical place for that information, isn't a good source.

Thank you again.

[Molandfreak]

I miss the like button 

Like

See, this is why it's handy. If someone posts something thoughtful or interesting that I have no further comment on, I like using it since we can no longer just post an emoticon in response to someone's post.

[Alex]

Just a note to say THANK YOU to Alex for all his hard work on the forum. The Pacific Southwest forum is one I depend upon as a primary source of information for my pages, as well as a primary place to promote when I do California Highway Headline posts, posts of updates to my pages, and posts about the California Highways podcast. It has always served as a relatively high quality source of information.

I know the incredible amount of work that goes into maintain all of this, and I just want to let @Alex know that I appreciate it.

The one suggestion I might make is to create a read-only, non-forum page off AARoads (e.g. .../forumstatus.html) that just provides a status update on the forum for downtimes like this. The AARoads FB page, which would be a logical place for that information, isn't a good source.

Thank you again.

Much appreciated Dan. I like your idea and will add that as an addition to my nearly complete site reprogramming.

I miss the like button 

Like

See, this is why it's handy. If someone posts something thoughtful or interesting that I have no further comment on, I like using it since we can no longer just post an emoticon in response to someone's post.

I don't disagree with you on this. It is that during the course of my debugging and code adjustments, the Likes script was part of a recursion error that generated incessantly:

Code Select Expand

2022 | 1747489305 |      6594 | D
▒g  | ?topic=18020.1750             | 2: Unknown: Cannot call session save handler in a recursive manner | 9bf262bec0956a41b08875ca9536d734 | general    | Unknown |    0 | [{"function":"smf_error_handler"}] |
|     2021 | 1747488610 |         0 | (M▒▒   | ?topic=10906.msg261197        | 2: Unknown: Cannot call session save handler in a recursive manner | 959f589879e9afad53248ff3c71675f9 | general    | Unknown |    0 | [{"function":"smf_error_handler"}] |
|     2020 | 1747487382 |         0 | 4▒▒▒    | ?topic=22572.msg2317834       | 2: Unknown: Cannot call session save handler in a recursive manner | f3e7f1bfb28018d2e3335073d4650b24 | general    | Unknown |    0 | [{"function":"smf_error_handler"}] |
|     2019 | 1747487209 |         0 | ▒˾▒    | ?topic=12138.0                | 2: Unknown: Cannot call session save handler in a recursive manner | 9a69812234fb96c3683991378bf0ce6d | general    | Unknown |    0 | [{"function":"smf_error_handler"}] |
|     2018 | 1747487208 |         0 | ▒˾▒    | ?topic=12138.0                | 2: Unknown: Cannot call session save handler in a recursive manner | 7c13142ee7c9d82c8af59de1aef4a8c5 | general    | Unknown |    0 | [{"function":"smf_error_handler"}] |
|     2017 | 1747487208 |         0 | ▒˾▒    | ?topic=12138.0                | 2: Unknown: Cannot call session save handler in a recursive manner | a26d2231f1f3f6808fb37bd747c8c851 | general    | Unknown |    0 | [{"function":"smf_error_handler"}] |
|     2016 | 1747487198 |         0 | 4▒▒▒    | ?topic=1224.msg2979417        | 2: Unknown: Cannot call session save handler in a recursive manner | b85130c98773c858c7f1a81cd84a7fce | general    | Unknown |    0 | [{"function":"smf_error_handler"}] |
|     2015 | 1747487102 |         0 | B▒D  | ?topic=11590.0;prev_next=prev | 2: Unknown: Cannot call session save handler in a recursive manner | e1bc74829e96601cb5c14bc013d45ed7 | general    | Unknown |    0 | [{"function":"smf_error_handler"}] |
|     2014 | 1747486515 |         0 | 4▒▒▒    | ?topic=22799.msg2541607       | 2: Unknown: Cannot call session save handler in a recursive manner | 793979d9cc5cb5d17f792a2caa87b584 | general    | Unknown |    0 | [{"function":"smf_error_handler"}] |
|     2013 | 1747486371 |         0 | 3▒▒   | ?topic=1492.msg39701          | 2: Unknown: Cannot call session save handler in a recursive manner | fa88003ecde62d7c793a8481b5f76c26 | general    | Unknown |    0 | [{"function":"smf_error_handler"}] |

Error Log (09:55:02 and later)
Stack traces show two errors related to checkSession() in Security.php, called from Likes.php:147:

Code Select Expand

[0x00007d2bd8013340] fatal_lang_error() /var/www/vhosts/aaroads.com/httpdocs/forum/Sources/Errors.php:237
[0x00007d2bd80131c0] checkSession() /var/www/vhosts/aaroads.com/httpdocs/forum/Sources/Security.php:710
[0x00007d2bd8013130] call() /var/www/vhosts/aaroads.com/httpdocs/forum/Sources/Likes.php:147

The stack trace points to Likes.php:147, where checkSession() is called during a "Like" action. SMF's checkSession() function (in Security.php) ensures a valid session before processing user actions. If an AJAX request (e.g., liking a post) triggers a session save while another session operation is active, PHP throws the recursion error.
This can happen if:
Multiple AJAX requests fire simultaneously (e.g., a user rapidly clicks "Like").
SMF's session handler is misconfigured or interfered with by another process.

Immediate Fix:
Modify Likes.php to avoid recursive session calls:

I attempted some code modifcation to address this, but the problem continued. I eventually decided to just deactivate Likes so I could move forward with getting the Forum to a stable state.

Session Recursion Error Resolution
Deactivating "Likes" (via Admin > Posts and Topics > Likes) was a smart move. The stack traces in the slow log (e.g., Likes.php:147 triggering checkSession()) confirm the error was tied to that feature. Since no new errors appear in the logs after 09:47:46, the issue is likely resolved.

I believe James was who activated the Likes aspect of SMF, so maybe he can restore it when he has some time.

[Alex]

The one suggestion I might make is to create a read-only, non-forum page off AARoads (e.g. .../forumstatus.html) that just provides a status update on the forum for downtimes like this. The AARoads FB page, which would be a logical place for that information, isn't a good source.

I have a script ready, and it will debut once I finish the AARoads backend reprogramming. It will query the SMF database and output users online and the most recent five posts in addition to a status message regarding if any SMF errors are currently logged. I'll adjust the text above it when forum downtime will occur of if I have to take it offline to address an ongoing problem with bots and the like.

I set up a cron job so that this will not be an actual live look at the forum, but instead be a snapshot generated every 5 minutes. This way the script is not actively querying the database anytime someone is accessing the forum status webpage. Programmingwise, this is encapsulated as a method to make it more efficient as well.

[MaxConcrete]

Thanks for the efforts to get the site back up.

Now I need to dedicate effort to restoring one of my web hosts.

Early this morning I received a message from the host of my DallasFreeways.com domain that "User dallasfr has used up 460% of their bandwidth and 88.4% of their allocated disk space" and "User dallasfr has been suspended for bandwidth overusage". This situation has never occurred in the 10 years I've used this host (webhostingpad). The long term trend for bandwidth on my sites is flat or down, so a bandwidth surge is unexpected.

So all content hosted on that site is unavailable. My host is totally suspended - I cannot even log in with FTP.

I use a directory on DallasFreeways.com for images which I posted on AA Roads. It appears that the bot is following links in posts on AA Roads and also instigating a DDoS attack on those links.

I have a few items on AA roads which are linked to files hosted on Azure. On May 5 and 6 file requests were 5 to 10 times normal rates. There are also spikes about 5x normal on May 12 and May 14. I can't say for a fact that these spikes were caused by the AA Roads DDoS bot, since I have only a few files linked on AA Roads and the overwhelming majority of requests to Azure are direct from dfwfreeways.com and houstonfreeways.com.

I've been in the process of migrating to Azure blob hosting, so I think this will force me to complete that process.