• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Remote Access
#11
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.
You never fail until you stop trying.“, Albert Einstein (1879 - 1955)

  Reply
#12
(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


Attached Files Thumbnail(s)
       
  Reply
#13
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
You never fail until you stop trying.“, Albert Einstein (1879 - 1955)

  Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  How to access netPI? firefly 6 39 May-16th-2019, 02:31 AM
Last Post: firefly
  Wi-Fi access problem MGharat 3 12 March-12th-2019, 09:27 AM
Last Post: Armin@netPI
  access to netPI MGharat 2 19 March-7th-2019, 07:16 AM
Last Post: Armin@netPI
  [SOLVED] Access problems Azzamjj 8 172 January-25th-2019, 07:43 AM
Last Post: Armin@netPI
  [INFO] RESTful API for Docker remote control Armin@netPI 0 89 December-17th-2018, 10:15 AM
Last Post: Armin@netPI
Information Managing netPI's Docker from remote via RESTful API for netPI versions < 1.1.4.0 Armin@netPI 4 282 September-7th-2018, 10:41 AM
Last Post: Armin@netPI
  [SOLVED] after WIFI enabled - no access paubau 7 262 August-30th-2018, 02:04 PM
Last Post: Armin@netPI
  Accessing Docker daemon through remote CLI adeeljsid 2 162 August-30th-2018, 12:32 PM
Last Post: Armin@netPI
  Resart/Access NetPi from Remote Jonas.Sellmann@outlook.de 11 391 August-1st-2018, 11:06 AM
Last Post: Jonas.Sellmann@outlook.de
  Access Denied to LED1 / LED2 crthomas1234 1 104 July-12th-2018, 04:36 PM
Last Post: Armin@netPI

Forum Jump:


Users browsing this thread: 1 Guest(s)