+- Hilscher Community Forum (https://forum.hilscher.com)
+-- Forum: netPI 3 - Docker featuring Industrial Raspberry Pi 3 platform (https://forum.hilscher.com/forum-1.html)
+--- Forum: Software (https://forum.hilscher.com/forum-5.html)
+--- Thread: Remote Access (/thread-321.html)
Pages:
1
2
RE: Remote Access - Armin@netPI - September-19th-2018
Well you said the problem comes up every 2-3 week on any netPI you have installed.
Even if we both think there is no relation between the error and the used disk space any more but still you can check from time to time with the command
df -h
for the used disk space on the system.
It will output you
Filesystem Size Used Avail Use% Mounted on
overlay 6.0G 1.2G 4.6G 21% /
tmpfs 64M 0 64M 0% /dev
tmpfs 461M 0 461M 0% /sys/fs/cgroup
/dev/dm-0 6.0G 1.2G 4.6G 21% /etc/hosts
shm 64M 0 64M 0% /dev/shm
tmpfs 461M 0 461M 0% /sys/firmware
The available disk space under /dev/dm-0 is the most important value.
You have the chance tomorrow to visit the netPI on-site. Please check if it can be recovered by a simple power on reset or if you have to do other things, like reinstalling the image or reloaded any of the containers. Maybe also it would be good to connect a display to the HDMI port during the first start to watch to log output.
But before installing anything use the very nice syslog feature in version 1.1.3.0. netPI saves all the problems found in a log file. So after the restart go to the web console under "system/syslog" and download the file found. You can send it to netpi@hilscher.com if you feel it contain proprietary information, otherwise append it to a post.
RE: Remote Access - Jonas.Sellmann@outlook.de - September-20th-2018
(September-19th-2018, 11:37 AM)Armin@netPI Wrote: Well you said the problem comes up every 2-3 week on any netPI you have installed.
Even if we both think there is no relation between the error and the used disk space any more but still you can check from time to time with the command
df -h
for the used disk space on the system.
It will output you
Filesystem Size Used Avail Use% Mounted on
overlay 6.0G 1.2G 4.6G 21% /
tmpfs 64M 0 64M 0% /dev
tmpfs 461M 0 461M 0% /sys/fs/cgroup
/dev/dm-0 6.0G 1.2G 4.6G 21% /etc/hosts
shm 64M 0 64M 0% /dev/shm
tmpfs 461M 0 461M 0% /sys/firmware
The available disk space under /dev/dm-0 is the most important value.
You have the chance tomorrow to visit the netPI on-site. Please check if it can be recovered by a simple power on reset or if you have to do other things, like reinstalling the image or reloaded any of the containers. Maybe also it would be good to connect a display to the HDMI port during the first start to watch to log output.
But before installing anything use the very nice syslog feature in version 1.1.3.0. netPI saves all the problems found in a log file. So after the restart go to the web console under "system/syslog" and download the file found. You can send it to netpi@hilscher.com if you feel it contain proprietary information, otherwise append it to a post.
Hello Armin,
today we restarted our netPi and after restart everything worked fine.
The output of the command df -h and of the control panel you can find in the attachements.
So we don't really know why the netPis sometimes has this errors, because now we can reach the website and the containers are running correctly.
I downloaded the syslog file and will send it to netpi@hilscher.com.
Thanks,
Jonas
RE: Remote Access - Armin@netPI - September-20th-2018
Thank you Jonas, we received the file and we will analyse it.
The pictures you have appended do indeed not show any problem. So I agree this is not a full SD card problem.
Just for matter of sychronization with the log file. Do you know exactly when you have called the "special reset" command? Can you reconstruct it the time?
Just in case: calling the "special reset" command worked here fine. Can you try it yourself again and see if your netPI is also resetting fine like my one?
Thx
Armin