Fossil User Forum

The server load is currently too high. Please try again later
Login

The server load is currently too high. Please try again later

The server load is currently too high. Please try again later

(1) By anonymous on 2025-04-14 13:14:39 [source]

FYI

The server load is currently too high. Please try again later.

Current load average: 4.381348.
Load average limit: 4.000000

This page was generated in about 0.007s by Fossil 2.26 [aac885a619] 2025-04-13 19:54:24 

(2) By Richard Hipp (drh) on 2025-04-14 13:22:51 in reply to 1 [link] [source]

What URL were you using that delivered this reply? When did you receive this message (in UTC)?

(3) By Richard Hipp (drh) on 2025-04-14 13:56:45 in reply to 2 [link] [source]

FWIW, the page that is painted when the server encounters an overload condition has now been updated to automatically provide the information I requested from anonymous.

(5) By Andy Bradford (andybradford) on 2025-04-14 14:29:34 in reply to 3 [link] [source]

> FWIW, the page that is  painted when the server encounters an overload
> condition

I too saw an overload condition a  few days ago after the new server was
put into production, however, I didn't  report it because I thought that
perhaps it  was just due to  the move, however, I  suppose it's possible
that  the new  hosting provider  is not  providing as  much IOPS  as the
previous home.

Guess we'll have to see if this becomes a more frequence occurrence.

Andy

(6) By Richard Hipp (drh) on 2025-04-14 14:34:10 in reply to 5 [link] [source]

They mystery to me is that my instrumentation shows that the load average never went above about 0.75 during the period that the overload was reported. So I'm wondering if there is some kind of glitch in the getloadavg() function on Alpine Linux?

(7) By DB (ACB) on 2025-04-14 20:01:01 in reply to 6 [link] [source]

I saw an error message repeatedly starting a few days ago, but like Andy I ignored it and slowly but surely, for me at least, it went away and pages started loading. Except the error wasn't from fossil; it was from the browser, along the lines of ~ The site can't be reached. Maybe it's too busy.

I've been busy, but took a look at the timeline once in a while and noticed caching activity happening.

But my problem is I'm not getting any emails informing me of posts and such.

The first time I checked the /forum/alerts my email was missing from the field, so I added it back. Then I checked that page a few days later and all my choices were unchecked except for "Announcements." So I checked the ones I wanted again, and now I see it's stable. But I'm still not receiving any email from the forum.

(8) By Richard Hipp (drh) on 2025-04-14 20:10:02 in reply to 7 [link] [source]

The server is in a different data center, so it came with a new IP address, and apparently an IP address that has in a previous life been used by spammers. So if you are using one of the blacklist services to filter email, it probably won't get through.

Notification emails are DKIM-signed and the SPF and DMARC settings are all correct. And reverse-DNS is correct. So email gets through to places like gmail and protonmail without any problems.

(9) By Dave St.Germain (davestg) on 2025-04-15 17:21:25 in reply to 8 [link] [source]

For what it's worth, I haven't received email notifications since April 7th. The last message came from the new server -- a1.sqlite.org -- but since then, I don't see any connection attempts in the mail server logs.

(10) By Richard Hipp (drh) on 2025-04-15 17:28:05 in reply to 9 [link] [source]

The email server at virginia.pobblelabs.org says "250 2.0.0 35cb2799 Message accepted for delivery". Please check your spam folder.

(11) By Dave St.Germain (davestg) on 2025-04-15 17:42:58 in reply to 10 [link] [source]

I received the test message, but no forum notifications since April 7th. Maybe it'll work from now on?

(I don't have a spam folder, but the rspamd logs show no connection attempts from a1.sqlite.org between the 7th and now)

(12) By Richard Hipp (drh) on 2025-04-15 23:39:44 in reply to 11 [link] [source]

The old server operated by writing outbound email messages into an SQLite database. Then a separate daemon that lived outside the chroot jail in which Fossil runs would poll that database and relay the messages on to users by invoking sendmail.

The new server operates by opening a socket to a local MTA (Mail Transfer Agent - OpenSMTPD in this case) and talking SMTP to the MTA to hand off the notification to the MTA. There could be something wrong in that Fossil-to-MTA connection. I have implemented improved diagnostics to try to track that down. This Forum post will be the first real test...

(13) By Richard Hipp (drh) on 2025-04-16 00:50:42 in reply to 12 [link] [source]

The previous message revealed that the SMTP connection was being reset after sending a subset of the notifications. I have now rejiggered the Relay notification method to retry after a failure. Perhaps this post will go better...

(14) By DB (ACB) on 2025-04-16 02:54:49 in reply to 13 [link] [source]

You kicked the correct tire. I'm now receiving emails again. :-) Now it's just a matter of catching up. :-)

Also, thank you for redeeming the IP from spam to something good. :-)

(4) By anonymous on 2025-04-14 14:00:46 in reply to 2 [link] [source]

What URL were you using that delivered this reply?

https://fossil-scm.org/forum/timeline?ss=v&y=f&n=20&vfx&nsm

When did you receive this message (in UTC)?

About 1 minute or so before made the post. So that would make it about 2025-04-14 13:13:39 +-

(15.1) By sean (jungleboogie) on 2025-04-16 18:11:19 edited from 15.0 in reply to 1 [link] [source]

I saw this in action just now...

The server load is currently too high. Please try again later.

Current load average: 4.547363
Load average limit: 4.000000
URL: https://fossil-scm.org/home/doc/trunk/www/index.wiki
Timestamp: 2025-04-16 18:03:50Z

Also same on sqlite.org/src and forum, but homepage of sqlite.org loaded without issue.

edit...could it have been when fossil was being built on the server? Seems like the fossil copy has been updated very frequently, though.