![]() |
![]() |
#496 |
A Sunny Moo
Aug 2007
USA (GMT-5)
3·2,083 Posts |
![]()
The noprimeleftbehind.net server appears to have suffered a hard reboot overnight. (The website was up and running fine, but the PRPnet servers were all down. The servers' lock files had not been cleaned up indicating the shutdown was hard.)
I've restarted all the PRPnet servers as of a few minutes ago. |
![]() |
![]() |
![]() |
#497 |
Jan 2006
deep in a while-loop
10100100102 Posts |
![]()
Thanks Max!
I just finished migrating my own servers to IPv6 DDNS The old address for the NPLB DR machine is no more (nplb.no-ip.org is now defunct) The NPLB DR host is now at noprimeleftbehind.dynv6.net Last fiddled with by AMDave on 2017-07-01 at 00:24 |
![]() |
![]() |
![]() |
#498 |
May 2007
Kansas; USA
72·211 Posts |
![]()
I just now got home from out of town. Thanks Max for taking care of that!
![]() |
![]() |
![]() |
![]() |
#499 |
"Jussi Heino"
Sep 2017
Finland
3 Posts |
![]()
www.noprimeleftbehind.net is not working for me (Finland/Europe).
Recent results in http://noprimeleftbehind.dynv6.net/s...content=recent are in the state of: Last update: 2017-11-17 02:11:22 Server Time: 2017-11-26 19:14:18 My result was the last one in... |
![]() |
![]() |
![]() |
#500 |
May 2007
Kansas; USA
241438 Posts |
![]()
I may have a hard drive issue. The machine shut down and I cannot get it to reboot. I will look more into it on Sunday afternoon.
All data is backed up relatively frequently so any loss of data would be minimal. |
![]() |
![]() |
![]() |
#501 |
May 2007
Kansas; USA
72×211 Posts |
![]()
I cannot get the machine to boot. Dave, what is the status of the backup?
|
![]() |
![]() |
![]() |
#502 |
May 2007
Kansas; USA
72·211 Posts |
![]()
Well, I determined that the problem is not the hard drive. In the various attempts at rebooting the machine I had messed up the boot area. I was able to run the fsck -v command and the computer booted up fine.
I then started the servers and it ran for a while. It accepted all work units that it was waiting on, sent out new ones, and then proceeded to reboot itself again for no particular reason. I'm now thinking I have a bad motherboard or possibly a bad power supply. I will try replacing the power supply. I have a few spares laying around. |
![]() |
![]() |
![]() |
#503 |
May 2007
Kansas; USA
72·211 Posts |
![]()
After replacing the power supply the machine still wants to intermittently reboot itself. Sometimes it goes a few hours, sometimes only a few minutes.
I'm guessing now that it is the motherboard. So...I'll keep the servers running as best as I can until I can get the motherboard replaced. |
![]() |
![]() |
![]() |
#504 |
May 2007
Kansas; USA
1033910 Posts |
![]()
I have moved the server machine hard drive to another machine and it no longer reboots itself. I confirmed that the new machine has internet access. I started the servers but nothing happens. No work units are being received or sent. Also CRUS's and NPLB's web pages are not accessible from the normal links on our projects.
The machine is very similar to the previous server machine. Slightly older motherboard and CPU both very similar. I feel like there is something wrong in the internet setup even though the machine connects fine to the internet. Does anyone have any ideas? |
![]() |
![]() |
![]() |
#505 |
Jan 2006
deep in a while-loop
2×7×47 Posts |
![]()
Apologies for the delay in responding. I did get sent the notification of your post but it was languishing in my spam filter.
The server is still sending me the log files so outbound comms is working and therefore I also have the IP address. We just need to fix the inbound routing, so that may be either on the router or DynDNS. I will be back home tonight so I'll get a good look at it then. Last restore on the DR machine was "Last update: 2017-11-17 02:11:22" http://noprimeleftbehind.dynv6.net/stats/ although I am still having an issue with the DynDNS automatic update but otherwise all good there. |
![]() |
![]() |
![]() |
#506 |
Jan 2006
deep in a while-loop
2·7·47 Posts |
![]()
It appears that the NPLB server is updating the dynamic DNS route correctly.
I have confirmed that the server is reporting the correct address and is updating the dynamic DNS index with the correct address. I have to suggest that there is a setting on the router connected to the server that is the issue. Perhaps the port-forward rule is bound to the old MAC address of NIC on the old motherboard. I cannot resolve it from here. If Max has some time he may be able to help check the router config, |
![]() |
![]() |
![]() |
Thread Tools | |
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
What exactly is sent to the server? | paul0 | NFS@Home | 2 | 2015-03-12 23:00 |
Server bug -- new? | Christenson | Information & Answers | 5 | 2011-07-12 21:44 |
Server Down? | Grant | Information & Answers | 13 | 2008-11-24 19:37 |
New ECM-server available | andi314 | Factoring | 3 | 2003-08-31 11:22 |
New Server Hardware and price quotes, Funding the server | Angular | PrimeNet | 32 | 2002-12-09 01:12 |