Search Failed.. (shortly forgot how to switch configuration)
Search Failed.. (shortly forgot how to switch configuration)
Receiving a message: An existing connection was forcibly closed by the remote host. (System 10054)
it is working now, just the second server system failed and i forgot how to switch the configuration right, because since the august there was no need to do it even once.
but right now the service is being run with 50 day retention on the backup server until the other server restarted.
with the failed server most likely need to replace power supply (i noticed some voltage deviations), the new power supply has already arrived also there will be another computer available shortly to do hardware tests thoroughly if power supply replacement won't help, faulty RAM is possible but unlikely.
but right now the service is being run with 50 day retention on the backup server until the other server restarted.
with the failed server most likely need to replace power supply (i noticed some voltage deviations), the new power supply has already arrived also there will be another computer available shortly to do hardware tests thoroughly if power supply replacement won't help, faulty RAM is possible but unlikely.
ok it has almost restarted.
when it does i'll switch the configuration first with the backup server still supplying full newsgroup range until the second server will catch up, then i'll restart backup server with picture groups only as usual.
at least it was an emergency drill how to switch to the backup server.
when it does i'll switch the configuration first with the backup server still supplying full newsgroup range until the second server will catch up, then i'll restart backup server with picture groups only as usual.
at least it was an emergency drill how to switch to the backup server.
i've restarted the backup server as the second server is now up to date.
after checking i think it is not hardware but some windows bug with remote login when access is sluggish, the system went unresponsive and the server stopped when i tried to login, then cancelled the login and tried to login again - it gave error creating login session. i just checked server running record when the server stopped getting headers against my first msn message when i mentioned the issue to someone shortly after it happened - the time is about the same, within few minutes, so it is unlikely there is other reason than the retried login which went wrong.
after checking i think it is not hardware but some windows bug with remote login when access is sluggish, the system went unresponsive and the server stopped when i tried to login, then cancelled the login and tried to login again - it gave error creating login session. i just checked server running record when the server stopped getting headers against my first msn message when i mentioned the issue to someone shortly after it happened - the time is about the same, within few minutes, so it is unlikely there is other reason than the retried login which went wrong.