Skip to content
View in the app

A better way to browse. Learn more.

Armbian Community Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

RAMLOG and LIRC not working on startup

Featured Replies

I'm currently running  ARMBIAN 5.31 Debian GNU/Linux 8 (jessie) 4.11.5-sunxi on my Cubietruck, which otherwise works fine as a headless data and media server. However, for quite some time (also on previous ARMBIAN builds) I get two failure messages every time I boot the system:

 

> [FAIL] Starting up cgroup management Error: /var/log is in use ... failed ! ramlog-tmpfs 2.0.0

In /var/log/boot it says:

Sat Jun 17 19:53:57 2017: INIT: Entering runlevel: 2
Sat Jun 17 19:53:57 2017: [^[[36minfo^[[39;49m] Using makefile-style concurrent boot in runlevel 2.
Sat Jun 17 19:53:59 2017: [....] Starting cgroup management daemon: cgmanager[....] Starting ramlog-tmpfs 2.0.0:
Sat Jun 17 19:54:00 2017: The list of open files: (You need to close below daemons if you want to start/stop ramlog manually)
Sat Jun 17 19:54:00 2017:
Sat Jun 17 19:54:00 2017: COMMAND  PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
Sat Jun 17 19:54:00 2017: lsusb   1502 root    1w   REG  179,1   186584 2284 /var/log/armhwinfo.log
Sat Jun 17 19:54:00 2017:
Sat Jun 17 19:54:00 2017: Test result: ramlog cannot be started or stopped at the moment.

 

As a consequence ramlog is not running !

On testing startstop function of ramlog I get the following:

root@CT:~# /etc/init.d/ramlog teststartstop
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
minidlnad 1499         minidlna    4w   REG  179,1     2018   2188 /var/log/minidlna.log
nmbd      1858             root    2w   REG  179,1     1863 128555 /var/log/samba/log.nmbd
nmbd      1858             root    8w   REG  179,1     1863 128555 /var/log/samba/log.nmbd
smbd      2056             root    2w   REG  179,1      933 128812 /var/log/samba/log.smbd
smbd      2056             root    8w   REG  179,1      933 128812 /var/log/samba/log.smbd
squeezebo 2093 squeezeboxserver    6w   REG  179,1   167550 128891 /var/log/squeezeboxserver/server.log
squeezebo 2093 squeezeboxserver    7w   REG  179,1        0 142384 /var/log/squeezeboxserver/perfmon.log

Test result: ramlog cannot be started or stopped at the moment.

 

The second boot-up failure message refers to LIRC not working:

 

> [FAIL] Starting remote control daemon(s) : LIRC : failed

In /var/log/boot log it says:

Sat Jun 17 19:54:08 2017: /etc/init.d/lirc: 1: /etc/lirc/hardware.conf: î\007SK9XJ¤\005í\00714.8.4-sunxiSK9X£Þ\005ñ\00744.8.4-sunxi: not found
Sat Jun 17 19:54:08 2017: [....] Starting remote control daemon(s) : LIRC :^[[?25l^[[?1c^[7^[[1G[^[[31mFAIL^[[39;49m^[8^[[?25h^[[?0c ^[[31mfailed!^[[39;49m
 

As I don't use any IR functions on the Cubietruck, this doesn't really matter, I suppose. But most likely there is a way to get rid of this error message. Trouble is I don't know it.

 

Any remedial aid would be appreciated, many thanx in advance !

 

Guest
This topic is now closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.