The current error that prevents posting, and shows content in the future.

Patrick

Overthinking the draft from the basement already
Staff member
Just throwing this here -
it is the local time of my chromebox compared to what the web server is reporting, compared
to the command line on our server.

1598187603 1598188208 605
Server date not equal to local call 0 1598187603 1598188208 605
Convert server time
Sun Aug 23 09:00:03 EDT 2020
Convert local time
Sun Aug 23 09:10:08 EDT 2020
local date from command line
Sun Aug 23 09:10:08 EDT 2020
Server date from command line
Sun Aug 23 06:10:09 PDT 2020

Note time zone diff in last one
 

Patrick

Overthinking the draft from the basement already
Staff member
I'll also note after posting that, the time was correct on the post, and going
back to my script produced the correct time on the server.
 

Patrick

Overthinking the draft from the basement already
Staff member
Not a computer guy here, but this is still a thing. On phone or pc.

View attachment 137776

it is still a thing, but it won't block posting anymore.
I'm working with our provider to find out why the time is occasionally off.
(We have an idea - just need to convince them)

it now manifests itself with weird crap like you see,
direct messages out of order, and when you ask for new-posts,
it displays ones you've read - although not bold.

The site hosting service is not free, so i expect them to give it some priority.
I made our case on Friday - (i did not go chad on them yet)
 

Patrick

Overthinking the draft from the basement already
Staff member
What is the server using for NPT? Is burn it to the ground and buy a new one a current voting option?

We are living in a shared hosting environment.
I tried to call meltdown() and newcomputer() but got a permissions error
and it threw a SPOUSEBLOCK code.

I'm not sure how the load is balanced between processors/virtual machines/blades....
and if they balance by IP so that session info is cached.
i doubt it is a true NTP issue (or lack of using it) - more likely some corruption, or library mis-match.

Once i start seeing the error, it is consistently off by about 10 minutes - but it is not the same all of the time.
Then it magically disappears. I can get the incorrect time error through the web interface, but if i run
the program directly from the command line it does not fail.

I can see that someone is posting in the past, but my call to get the time is correct - so def being
serviced by different nodes/instances or whatever the term is.
 

jdgang

Well-Known Member
I just tried those two subroutines for a new PC for myself and received the same SPOUSEBLOCK code. I guess those are the only two universal API calls in the world. That being said, i am not the F5 admin here, and its something i dont want to learn
 

Patrick

Overthinking the draft from the basement already
Staff member
Its not all the time. Happens once in a while across 3 devices... my android phone, MacBook and ipad mini.

all from your home?

I gotta say -

1598470017145.png

Or you have one of those DNS attacks, or spyware.
 
Top Bottom