I have been having off and on again issues with the server web interface being unavailable.  I've done some troubleshooting and have narrowed it down to when I leave my VM running for an extended period of time.  It is annoying to have to remember to shut down my VM every 2 or 3 days or risk losing connectivity to my server. 

 

I am running Version 6.1.9 and am attaching the syslog from when it last happened.

 

Thanks in advance for any assistance.

system_log.txt

I have been having off and on again issues with the server web interface being unavailable.  I've done some troubleshooting and have narrowed it down to when I leave my VM running for an extended period of time.  It is annoying to have to remember to shut down my VM every 2 or 3 days or risk losing connectivity to my server. 

 

I am running Version 6.1.9 and am attaching the syslog from when it last happened.

 

Thanks in advance for any assistance.

There were many updates in the latest versions, both security and function, that may effect this behavior. Please updated to 6.2.3 and see if you are still having issues. Also, when posting for assistance, please upload the whole diagnostics.zip file instead of just the syslog.

 

When updating from 6.1.9 to 6.2.3, there are several possible gotcha's that need to be addressed, so be sure to thoroughly read and understand the upgrade instructions, and post back after reading if you have any questions about the procedure.

Thanks for the info.  I'll take a look at the upgrade instructions and see if anything doesn't make sense.

I have been having off and on again issues with the server web interface being unavailable.  I've done some troubleshooting and have narrowed it down to when I leave my VM running for an extended period of time.  It is annoying to have to remember to shut down my VM every 2 or 3 days or risk losing connectivity to my server. 

 

I am running Version 6.1.9 and am attaching the syslog from when it last happened.

 

Thanks in advance for any assistance.

There were many updates in the latest versions, both security and function, that may effect this behavior. Please updated to 6.2.3 and see if you are still having issues. Also, when posting for assistance, please upload the whole diagnostics.zip file instead of just the syslog.

 

When updating from 6.1.9 to 6.2.3, there are several possible gotcha's that need to be addressed, so be sure to thoroughly read and understand the upgrade instructions, and post back after reading if you have any questions about the procedure.

 

Is there a command line prompt to get the diagnostics.zip file?  I only know how to get the syslog file from the command prompt when the system locks up.

Is there a command line prompt to get the diagnostics.zip file?  I only know how to get the syslog file from the command prompt when the system locks up.

This sticky post at the top of this forum is a good place to start.

https://lime-technology.com/forum/index.php?topic=39257.0

I have been having off and on again issues with the server web interface being unavailable.  I've done some troubleshooting and have narrowed it down to when I leave my VM running for an extended period of time.  It is annoying to have to remember to shut down my VM every 2 or 3 days or risk losing connectivity to my server. 

 

I am running Version 6.1.9 and am attaching the syslog from when it last happened.

 

Thanks in advance for any assistance.

There were many updates in the latest versions, both security and function, that may effect this behavior. Please updated to 6.2.3 and see if you are still having issues. Also, when posting for assistance, please upload the whole diagnostics.zip file instead of just the syslog.

 

When updating from 6.1.9 to 6.2.3, there are several possible gotcha's that need to be addressed, so be sure to thoroughly read and understand the upgrade instructions, and post back after reading if you have any questions about the procedure.

 

Either I did something wrong, or I missed a "gotcha". 

 

When I updated from 6.1.9 to 6.2.3 I lost network connectivity.  There was no link light on the card.  I did the upgrade twice.  Once from the plugins tab, and once by downloading the new version and moving the files to my boot flash drive.  Both these methods resulted in no network connectivity.  I thought I would try 6.3.0-rc3 to see if that would be any different, and that too left me with no network connectivity.  I have set everything back to 6.1.9 and everything is working as before.

 

Is this something simple like a NIC driver?  I am using a Intel EXPI9301CT Gigabit PCIe X1 Adapter in a Dell Precision 690 workstation.

 

Thanks in advance for any suggestions.

I have been having off and on again issues with the server web interface being unavailable.  I've done some troubleshooting and have narrowed it down to when I leave my VM running for an extended period of time.  It is annoying to have to remember to shut down my VM every 2 or 3 days or risk losing connectivity to my server. 

 

I am running Version 6.1.9 and am attaching the syslog from when it last happened.

 

Thanks in advance for any assistance.

There were many updates in the latest versions, both security and function, that may effect this behavior. Please updated to 6.2.3 and see if you are still having issues. Also, when posting for assistance, please upload the whole diagnostics.zip file instead of just the syslog.

 

When updating from 6.1.9 to 6.2.3, there are several possible gotcha's that need to be addressed, so be sure to thoroughly read and understand the upgrade instructions, and post back after reading if you have any questions about the procedure.

 

Either I did something wrong, or I missed a "gotcha". 

 

When I updated from 6.1.9 to 6.2.3 I lost network connectivity.  There was no link light on the card.  I did the upgrade twice.  Once from the plugins tab, and once by downloading the new version and moving the files to my boot flash drive.  Both these methods resulted in no network connectivity.  I thought I would try 6.3.0-rc3 to see if that would be any different, and that too left me with no network connectivity.  I have set everything back to 6.1.9 and everything is working as before.

 

Is this something simple like a NIC driver?  I am using a Intel EXPI9301CT Gigabit PCIe X1 Adapter in a Dell Precision 690 workstation.

 

Thanks in advance for any suggestions.

The best way to troubleshoot is to collect the diagnostics zip file while it's running 6.1.9, then upgrade and collect the diagnostics again, using the local console since you will have no network. Post both diagnostics, then we can see what went wrong.

Is this something simple like a NIC driver?  I am using a Intel EXPI9301CT Gigabit PCIe X1 Adapter in a Dell Precision 690 workstation.

 

If the onboard NIC is enable it's possible eth0 switched, if you have a monitor attached (or IPMI) don't forget that on v6.2 you can boot with the GUI option and use the builtin browser to easily check and setup your lan settings.

Is this something simple like a NIC driver?  I am using a Intel EXPI9301CT Gigabit PCIe X1 Adapter in a Dell Precision 690 workstation.

 

If the onboard NIC is enable it's possible eth0 switched, if you have a monitor attached (or IPMI) don't forget that on v6.2 you can boot with the GUI option and use the builtin browser to easily check and setup your lan settings.

Here is an update:

I found that eth0 was enabled in the BIOS so I disabled that.  When I booted to 6.2.3 I got an error saying that eth0 was unavailable and the console continuously beeped until I did a ctrl C.  I turned eth0 back on and rebooted into GUI mode. Still no network connectivity. I was able to get a diagnostic log from there, but it says it is corrupt and wouldn't open.  I rebooted into non GUI mode and ran the command prompt to get the diagnostic zip file.  This one as well was called corrupt.  I am not able to attach it to this post.

tower-diagnostics-20161105-1413.zip

tower-diagnostics-20161105-1413.zip

Boot using the GUI mode, go to settings -> network settings -> interface rules and choose the correct NIC as eth0, reboot and you your should be good to go.

Boot using the GUI mode, go to settings -> network settings -> interface rules and choose the correct NIC as eth0, reboot and you your should be good to go.

 

This appears to have worked. 

 

Since I was able to get it more stable, I booted back into the BIOS and de-activated eth0.  When I rebooted back to GUI, there was only one NIC option in the network settings and it was my Intel Gig card.  I have had the VM up for 12 hours now without it losing network connectivity.  I'll let it go and see if it locks up.

 

Thanks everyone for the support/suggestions.