Omega Owners Forum
Chat Area => General Discussion Area => Topic started by: TheBoy on 04 September 2023, 07:34:52
-
Did anybody try to access OOF from around 12:45am to 7:20am, and if so, was it working?
-
Around 5:30 it was showing timeout, not tried again until just now, where it seems fine ;D
-
I tried it about 10 minutes ago and it came up "This site cannot be reached" but came back to it just now and all fine.
-
It was timing out at 7.05am
-
And about 6:45
-
Wasn’t working around 2am
-
not working at 05:30 this morning
-
OK, ta. No idea why, but suspected that was the case. Everything looked to be working, only it wasn't.
Lemme know if there is a reoccurrence.
-
Did anybody try to access OOF from around 12:45am to 7:20am, and if so, was it working?
Yes and no. Unsure of exact times, but currently in Seattle.
-
7.20AM is the middle of the night.
I've been asleep for 3 or 4 hors at this point. :)
-
7.20AM is the middle of the night.
I've been asleep for 3 or 4 hors at this point. :)
I can imagine. Up watching your, erm, instructional videos till the early hours :-X
-
Gave the £D printer something to do and kludged up a 12cm fan on top of the router, plugging into the USB (its a 12v fan, so running quietly and at a modest speed. CPU temps dropped about 12C
Hopefully that will prevent reoccurrence, as have a suspicion it might have overheated...
-
Clearly it was not the heat then :(
-
Ahhhh! I wonder... ...surely not...
Lets see what happens tonight at midnight :(
-
I tried to access the site around 5/6am but it just timed out :-\
-
No access at 00:44am 5th Sept. "can't reach this page".
-
Hopefully resolved now, working ok before I left this morning.
Looks like my hunch was right, and was down to the now disabled acme client :(
-
2 days running, no more blocking all packets in the early hours.
Classing as fixed (but do need to get acmeclient running again at some point).
-
Was struggling to load pages at around 1-2 am :-\
-
Was struggling to load pages at around 1-2 am :-\
This morning?
Apache logs show it was getting hits overnight...
Next time, can you make a note of approx times, and if it was an error, or page just not responding, so I can look into it? Looks to be a different cause, either way.
-
Took too long to respond was the error message.
Will try to remember to screen shot it to note the time :y
-
Took too long to respond was the error message.
Will try to remember to screen shot it to note the time :y
That's a timeout I suspect.
So next time, grab exact time (in UTC or GMT to make it easy for me ;D), and I can check apache logs to see if you're even hitting it.
-
UTC/GMT I can manage ;D
Might be local by accident :D
-
1747 today ;) Took too long to respond was the gist of the error message.