Jump to content

[Banana]" Error ramlog" armbian 3.2 Kernel 3.4.108


sgei

Recommended Posts

Hi Igor,

 

I've installed a clean version of your image for BananaPi:

 

Hardware: BananaPi

Image-Version: 3.2 Kernel 3.4.108 Debian Wheezy

 

Installed Packages:

 

zip, unzip

ftp

dialog

xorg

lxde

slim

tightvncserver

 

I get the following ErrorMessage:

 

Boot

 

Jul 12 06:03:11 Enabling ramlog...                                       [ OK ]
Jul 12 06:03:14 Disabling ramlog...                                      [ OK ]
Jan 01 01:00:44 Enabling ramlog...                                       [ OK ]
Jul 24 08:01:08 Stopping ramlog: Error: ramlog is not running            [fail]
Jul 24 08:02:04 Starting ramlog-tmpfs 2.0.0:                             [ OK ]
Jul 24 08:23:29 Saving logs to hdd:                                      [ OK ]
Jul 24 08:23:30 Stopping ramlog:                                         [ OK ]
Jul 24 08:24:12 Starting ramlog-tmpfs 2.0.0:                             [ OK ]
Jul 24 08:29:22 Saving logs to hdd:                                      [ OK ]
Jul 24 08:29:22 Stopping ramlog:                                         [ OK ]
Jul 24 08:30:04 Starting ramlog-tmpfs 2.0.0:                             [ OK ]
Jul 24 11:07:43 Saving logs to hdd:                                      [ OK ]
Jul 24 11:07:45 Stopping ramlog:                                         [ OK ]
Jul 24 11:08:31 Starting ramlog-tmpfs 2.0.0:                             [ OK ]
Jul 24 11:39:22 Saving logs to hdd:                                      [ OK ]
Jul 24 11:39:22 Stopping ramlog:                                         [ OK ]
Jul 24 11:40:02 Starting ramlog-tmpfs 2.0.0:                             [ OK ]
Jul 24 11:46:09 Saving logs to hdd:                                      [ OK ]
Jul 24 11:46:10 Stopping ramlog:                                         [ OK ]
Jul 24 11:47:05 Starting ramlog-tmpfs 2.0.0:                             [ OK ]
Jul 24 11:54:24 Saving logs to hdd:                                      [ OK ]
Jul 24 11:54:24 Stopping ramlog:                                         [ OK ]
Jan 01 01:00:17 Starting ramlog-tmpfs 2.0.0:                             [ OK ]
Jul 24 13:23:54 Saving logs to hdd:                                      [ OK ]
Jul 24 13:23:59 Stopping ramlog:                                         [ OK ]
Jul 24 13:24:45 Starting ramlog-tmpfs 2.0.0:                             [ OK ]
Jul 24 13:40:13 Saving logs to hdd:                                      [ OK ]
Jul 24 13:40:19 Stopping ramlog:                                         [ OK ]
Jul 24 13:41:09 Starting ramlog-tmpfs 2.0.0: Error: /var/log is in use... [fail]
Jul 24 13:41:09 The list of open files: (You need to close below daemons if you want to start/stop ramlog manually)

COMMAND  PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
slim    1999 root    3w   REG  179,1      334 1598 /var/log/slim.log
sh      2002 root    3w   REG  179,1      334 1598 /var/log/slim.log
Jul 24 13:41:09 Test result: ramlog cannot be started or stopped at the moment.
Jul 24 13:46:19 ramlog: Cannot find shutdown flag file.                  [warning]
Jul 24 13:46:19 Stopping ramlog: Error: ramlog is not running            [fail]
Jul 24 13:47:00 Starting ramlog-tmpfs 2.0.0: Error: /var/log is in use... [fail]
Jul 24 13:47:01 The list of open files: (You need to close below daemons if you want to start/stop ramlog manually)
 

COMMAND  PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
slim    1980 root    3w   REG  179,1      677 1598 /var/log/slim.log
Xorg    1992 root    0w   REG  179,1        0  745 /var/log/Xorg.0.log.old
Xorg    1992 root    3w   REG  179,1      677 1598 /var/log/slim.log
Jul 24 13:47:01 Test result: ramlog cannot be started or stopped at the moment.
Jul 24 14:04:32 ramlog: Cannot find shutdown flag file.                  [warning]
Jul 24 14:04:33 Stopping ramlog: Error: ramlog is not running            [fail]
Jul 24 14:05:14 Starting ramlog-tmpfs 2.0.0: Error: /var/log is in use... [fail]
Jul 24 14:05:15 The list of open files: (You need to close below daemons if you want to start/stop ramlog manually)

COMMAND  PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
slim    1981 root    3w   REG  179,1      910 1598 /var/log/slim.log
Jul 24 14:05:15 Test result: ramlog cannot be started or stopped at the moment.

 

 

Shutdown/Reboot:

 

[warn] ramlog: Cannot find shutdown flag file. ... (warning)

[FAIL] Cannot find shutdown flag file. [.......] Stopping ramlog: Error: ramlog is not running Failed!

 

 

Can you help me?

 

Steffen

Link to comment
Share on other sites

I would suggest to disable ramlog service with:

service ramlog disable

it's disabled after reboot. If you upgraded to Jessie, Ramlog can't work - not compatible with systemd. 

 

If you are still on Wheezy than try to tweak the boot sequence. Ramlog should be started as early as possible.

Link to comment
Share on other sites

Uh :unsure:  No ideas for a simple strait answer. It's not simple but also not so complex.

 

http://askubuntu.com/questions/18802/how-to-correctly-add-a-custom-daemon-to-init-d

http://minecraft.gamepedia.com/Tutorials/Server_startup_script

 

Try google for more info if this is not enough.

 

It's strange because I use similar desktop configuration and it's working without a problem. Also it's pity that Ramlog is not supported anymore: http://www.tremende.com/ramlog/ Try to ping author  ;)

Link to comment
Share on other sites

Hi Igor,

 

With these two lines in LSB-Tags of ramlog I don't get any Errors:

 

# X-Stop-After: $syslog
# X-Interactive: true

 

Source: https://debianforum.de/forum/viewtopic.php?f=27&t=131540

### BEGIN INIT INFO
# Provides: ramlog
# Required-Start:
# Should-Start: $local_fs
# Required-Stop:
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: moves /var/log into ramdisk
# Description: ramlog daemon moves /var/log to ramdisk on startup and copies it back to harddrive on shutdown or restart
#
# X-Stop-After: $syslog
# X-Interactive: true
### END INIT INFO

Steffen

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines