Posts by Moreno

Moreno · Jun 20th 2023

Thanks for your help.

Have a nice day.

Moreno · Jun 19th 2023

Do you think, it can be solved in next update of Raspbian OS?

Moreno · Jun 19th 2023

this is the outpost of dpkg -l | grep keyring :

Code

dpkg -l | grep keyring
ii  openmediavault-keyring               1.0.2-2                          all          GnuPG archive keys of the openmediavault archive
ii  raspbian-archive-keyring             20120528.2                       all          GnuPG archive keys of the raspbian archive

Result of debian-archive-keyring :

Code

debian-archive-keyring
bash: debian-archive-keyring: command not found

Result of apt-get --allow-unauthenticated install debian-archive-keyring :

Code

apt-get --allow-unauthenticated install debian-archive-keyring
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'raspbian-archive-keyring' instead of 'debian-archive-keyring'
raspbian-archive-keyring is already the newest version (20120528.2).
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.

Result of apt-get --allow-unauthenticated install raspbian-archive-keyring :

Code

apt-get --allow-unauthenticated install raspbian-archive-keyring
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
raspbian-archive-keyring is already the newest version (20120528.2).
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.

Moreno · Jun 19th 2023

Really sorry, I thought it was the result of the SALT error and that I had forgotten something, but on attachments you have this files with this infos.

I think it's just and error with a depot, no?

Thanks for your help.

Moreno · Jun 19th 2023

Hi,

Since i have update my OMV (on my PI4) i have this message on OMV Web GUI :

When i click on apply after few moment of waiting, i have this message :

During the update i have same problem like here : https://www.openmediavault.org/?p=3477

But even with an reboot, this message continue to block the correct apply i think.

Do you have an solution?

Have a nice day.

Moreno · May 2nd 2023

Hi,

My problem is sovled i think, i have no problem since the last message.

Thanks for your help.

Moreno · Apr 20th 2023

After a reboot of my pi, it's works without any modification, just my old save, update OMV OS, install Docker and reboot...

Another X files of IT systems...

I'm waiting some days and i will make this topic solved if it's done.

Moreno · Apr 19th 2023

Code

root@raspberrypi:/home/pi# systemctl status docker.service
● docker.service - Docker Application Container Engine
     Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/docker.service.d
             └─waitAllMounts.conf
     Active: failed (Result: exit-code) since Wed 2023-04-19 10:47:45 CEST; 48s ago
TriggeredBy: ● docker.socket
       Docs: https://docs.docker.com
    Process: 3462 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status>
   Main PID: 3462 (code=exited, status=1/FAILURE)
        CPU: 362ms

Apr 19 10:47:45 raspberrypi systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Apr 19 10:47:45 raspberrypi systemd[1]: Stopped Docker Application Container Engine.
Apr 19 10:47:45 raspberrypi systemd[1]: docker.service: Start request repeated too quickly.
Apr 19 10:47:45 raspberrypi systemd[1]: docker.service: Failed with result 'exit-code'.
Apr 19 10:47:45 raspberrypi systemd[1]: Failed to start Docker Application Container Engine.
lines 1-16/16 (END)

Display More

Code

root@raspberrypi:/home/pi# journalctl -xe
░░
░░ The user manager instance for user 1000 has been started. All services queued
░░ for starting have been started. Note that other services might still be starting
░░ up or be started at any later time.
░░
░░ Startup of the manager took 513276 microseconds.
Apr 19 10:48:30 raspberrypi systemd[1]: Started User Manager for UID 1000.
░░ Subject: A start job for unit user@1000.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit user@1000.service has finished successfully.
░░
░░ The job identifier is 5675.
Apr 19 10:48:30 raspberrypi systemd[1]: Started Session 21 of user pi.
░░ Subject: A start job for unit session-21.scope has finished successfully
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit session-21.scope has finished successfully.
░░
░░ The job identifier is 5784.
Apr 19 10:48:31 raspberrypi sudo[3610]:       pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/usr/bin/su
Apr 19 10:48:31 raspberrypi sudo[3610]: pam_unix(sudo:session): session opened for user root(uid=0) by pi(uid=1000)
Apr 19 10:48:31 raspberrypi su[3611]: (to root) pi on pts/0
Apr 19 10:48:31 raspberrypi su[3611]: pam_unix(su:session): session opened for user root(uid=0) by pi(uid=0)
Apr 19 10:49:01 raspberrypi CRON[3785]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Apr 19 10:49:01 raspberrypi CRON[3787]: (root) CMD (/usr/sbin/omv-ionice >/dev/null 2>&1)
Apr 19 10:49:01 raspberrypi CRON[3785]: pam_unix(cron:session): session closed for user root
lines 1828-1856/1856 (END)
░░
░░ The user manager instance for user 1000 has been started. All services queued
░░ for starting have been started. Note that other services might still be starting
░░ up or be started at any later time.
░░
░░ Startup of the manager took 513276 microseconds.
Apr 19 10:48:30 raspberrypi systemd[1]: Started User Manager for UID 1000.
░░ Subject: A start job for unit user@1000.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit user@1000.service has finished successfully.
░░
░░ The job identifier is 5675.
Apr 19 10:48:30 raspberrypi systemd[1]: Started Session 21 of user pi.
░░ Subject: A start job for unit session-21.scope has finished successfully
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit session-21.scope has finished successfully.
░░
░░ The job identifier is 5784.
Apr 19 10:48:31 raspberrypi sudo[3610]:       pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/usr/bin/su
Apr 19 10:48:31 raspberrypi sudo[3610]: pam_unix(sudo:session): session opened for user root(uid=0) by pi(uid=1000)
Apr 19 10:48:31 raspberrypi su[3611]: (to root) pi on pts/0
Apr 19 10:48:31 raspberrypi su[3611]: pam_unix(su:session): session opened for user root(uid=0) by pi(uid=0)
Apr 19 10:49:01 raspberrypi CRON[3785]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Apr 19 10:49:01 raspberrypi CRON[3787]: (root) CMD (/usr/sbin/omv-ionice >/dev/null 2>&1)
Apr 19 10:49:01 raspberrypi CRON[3785]: pam_unix(cron:session): session closed for user root
~
~

Display More

i have found this while ago but not solving my problem :

[Solved] Docker service fail to start after update

Hello 👋 This morning, I update my docker installation on ubuntu 22.04 to version 23.0.0. I have a configuration to use another partition for my docker stuff,…

forums.docker.com

Moreno · Apr 18th 2023

Hi,

ryecoaaron , same error with a save (fresh install of docker on old save updated before installation of docker).

Code

Setting up docker-ce (5:23.0.4-1~debian.11~bullseye) ...
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.
invoke-rc.d: initscript docker, action "start" failed.
● docker.service - Docker Application Container Engine
     Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/docker.service.d
             └─waitAllMounts.conf
     Active: activating (auto-restart) (Result: exit-code) since Tue 2023-04-18 14:14:17 CEST; 21ms ago
TriggeredBy: ● docker.socket
       Docs: https://docs.docker.com
    Process: 8580 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
   Main PID: 8580 (code=exited, status=1/FAILURE)
        CPU: 338ms
dpkg: error processing package docker-ce (--configure):
 installed docker-ce package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 docker-ce

Display More

Moreno · Apr 17th 2023

ryecoaaron, i just want to update OMV on my PI without errors after update.

here is the result of the comand :

Code

dpkg -l | grep apparmor
ii  libapparmor1:armhf                   2.13.6-10                        armhf        changehat AppArmor library

I have added apparmor=0 at the end of line

Code

console=serial0,115200 console=tty1 root=PARTUUID=3f20dcc7-02 rootfstype=ext4 fsck.repair=yes rootwait apparmor=0

But after a reboot and tryied to update with APT, same problem :

Code

Setting up docker-ce (5:23.0.3-1~debian.11~bullseye) ...
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.
invoke-rc.d: initscript docker, action "restart" failed.
● docker.service - Docker Application Container Engine
     Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/docker.service.d
             └─waitAllMounts.conf
     Active: activating (auto-restart) (Result: exit-code) since Mon 2023-04-17 16:37:43 CEST; 24ms ago
TriggeredBy: ● docker.socket
       Docs: https://docs.docker.com
    Process: 16610 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
   Main PID: 16610 (code=exited, status=1/FAILURE)
        CPU: 362ms
dpkg: error processing package docker-ce (--configure):
 installed docker-ce package post-installation script subprocess returned error exit status 1
Setting up libraspberrypi-dev (1:2+git20230322~143557+9d5250f-1) ...

Display More

Moreno · Apr 17th 2023

hi,

I havent restored my system since i have this problem so now it works.

But since January or february i think i cant update my OMV, we are at the end of April soon...

I'm runing Dokcer and portainer.

I'm waiting an solution for PIs, but i dont see any solution for solving this problem...

Have a nice day.

Moreno · Apr 13th 2023

Hello,

I have same problem :

Code

Setting up docker-ce (5:23.0.3-1~debian.11~bullseye) ...
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.
invoke-rc.d: initscript docker, action "restart" failed.
● docker.service - Docker Application Container Engine
     Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/docker.service.d
             └─waitAllMounts.conf
     Active: activating (auto-restart) (Result: exit-code) since Thu 2023-04-13 11:27:11 CEST; 25ms ago
TriggeredBy: ● docker.socket
       Docs: https://docs.docker.com
    Process: 2065 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
   Main PID: 2065 (code=exited, status=1/FAILURE)
        CPU: 311ms
dpkg: error processing package docker-ce (--configure):
 installed docker-ce package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 docker-ce
E: Sub-process /usr/bin/dpkg returned an error code (1)

Display More

Content of my apparmor file :

Code

GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT extraargs=apparmor=0"

I have an PI4 (without grub, why ? i dont know..), so i have tryed with the solution with and without "extraargs=" befor apparmor.

Moreno · Apr 10th 2023

Hi,

No update? No idea of the problem?

Moreno · Mar 14th 2023

the problem is after the installation of update docker-ce, but i will try it today, thanks

EDIT :

Having always the original problem :

Code

Setting up docker-ce (5:23.0.1-1~debian.11~bullseye) ...
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.
invoke-rc.d: initscript docker, action "restart" failed.
● docker.service - Docker Application Container Engine
     Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/docker.service.d
             └─waitAllMounts.conf
     Active: activating (auto-restart) (Result: exit-code) since Tue 2023-03-14 11:13:05 CET; 22ms ago
TriggeredBy: ● docker.socket
       Docs: https://docs.docker.com
    Process: 3041 ExecStartPre=/bin/sleep 30 (code=exited, status=0/SUCCESS)
    Process: 3054 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
   Main PID: 3054 (code=exited, status=1/FAILURE)
        CPU: 373ms
dpkg: error processing package docker-ce (--configure):
 installed docker-ce package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 docker-ce
E: Sub-process /usr/bin/dpkg returned an error code (1)

Display More

Result of systemctl status docker.service

Code

@raspberrypi:/etc/systemd/system/docker.service.d# systemctl status docker.service
● docker.service - Docker Application Container Engine
     Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/docker.service.d
             └─waitAllMounts.conf
     Active: failed (Result: exit-code) since Tue 2023-03-14 11:14:13 CET; 25s ago
TriggeredBy: ● docker.socket
       Docs: https://docs.docker.com
    Process: 3116 ExecStartPre=/bin/sleep 30 (code=exited, status=0/SUCCESS)
    Process: 3129 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
   Main PID: 3129 (code=exited, status=1/FAILURE)
        CPU: 369ms

Mar 14 11:14:13 raspberrypi systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Mar 14 11:14:13 raspberrypi systemd[1]: Stopped Docker Application Container Engine.
Mar 14 11:14:13 raspberrypi systemd[1]: docker.service: Start request repeated too quickly.
Mar 14 11:14:13 raspberrypi systemd[1]: docker.service: Failed with result 'exit-code'.
Mar 14 11:14:13 raspberrypi systemd[1]: Failed to start Docker Application Container Engine.

Display More

Moreno · Mar 13th 2023

Hello, same issue here, i havent found solution on the web..

Moreno · Apr 5th 2022

for my personnal info : Why i have a lot of cron log without adding cron tasks?

Quote from macom

It is a feature, not a problem in itself.

If it is causing a problem on your system, you can use the solution from a previous post

Post

RE: Folder2ram filesystem full

If it is only these 15 entries per hour it should not be an issue.

To limit the size of the journal you can edit the conf file with
nano /etc/systemd/journald.conf
and add a line like
SystemMaxUse=100M
This will limit the size to 100MB. You can use other values.
After that restart the service with
systemctl restart systemd-journald

macom

Mar 19th 2022

Moreno · Apr 2nd 2022

so it's a problem with OMV?

Moreno · Mar 30th 2022

thanks for the information.

For my last post with log file, is a problem no?

because it's all the day, all the week, like an bad cron configuration.

Moreno · Mar 27th 2022

intresting thing i have this on my journalctl file (for all day, all of 3 or 4 minutes) :

Code

Mar 14 15:55:55 raspberrypi rngd[709]: stats: Time spent starving for entropy: (min=0; avg=0.000; max=0)us
Mar 14 15:56:01 raspberrypi CRON[26017]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 14 15:56:01 raspberrypi CRON[26018]: (root) CMD (/usr/sbin/omv-ionice >/dev/null 2>&1)
Mar 14 15:56:01 raspberrypi CRON[26017]: pam_unix(cron:session): session closed for user root
Mar 14 15:57:01 raspberrypi CRON[26026]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 14 15:57:01 raspberrypi CRON[26027]: (root) CMD (/usr/sbin/omv-ionice >/dev/null 2>&1)
Mar 14 15:57:01 raspberrypi CRON[26026]: pam_unix(cron:session): session closed for user root
Mar 14 15:58:01 raspberrypi CRON[26037]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 14 15:58:01 raspberrypi CRON[26038]: (root) CMD (/usr/sbin/omv-ionice >/dev/null 2>&1)
Mar 14 15:58:01 raspberrypi CRON[26037]: pam_unix(cron:session): session closed for user root
Mar 14 15:59:01 raspberrypi CRON[26047]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 14 15:59:01 raspberrypi CRON[26048]: (root) CMD (/usr/sbin/omv-ionice >/dev/null 2>&1)
Mar 14 15:59:01 raspberrypi CRON[26047]: pam_unix(cron:session): session closed for user root
Mar 14 16:00:02 raspberrypi CRON[26056]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 14 16:00:02 raspberrypi CRON[26057]: (root) CMD (/usr/sbin/omv-ionice >/dev/null 2>&1)
Mar 14 16:00:02 raspberrypi CRON[26056]: pam_unix(cron:session): session closed for user root
Mar 14 16:01:01 raspberrypi CRON[26066]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 14 16:01:01 raspberrypi CRON[26067]: (root) CMD (/usr/sbin/omv-ionice >/dev/null 2>&1)
Mar 14 16:01:01 raspberrypi CRON[26066]: pam_unix(cron:session): session closed for user root
Mar 14 16:02:01 raspberrypi CRON[26075]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 14 16:02:01 raspberrypi CRON[26076]: (root) CMD (/usr/sbin/omv-ionice >/dev/null 2>&1)
Mar 14 16:02:01 raspberrypi CRON[26075]: pam_unix(cron:session): session closed for user root
Mar 14 16:03:01 raspberrypi CRON[26088]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 14 16:03:01 raspberrypi CRON[26089]: (root) CMD (/usr/sbin/omv-ionice >/dev/null 2>&1)
Mar 14 16:03:01 raspberrypi CRON[26088]: pam_unix(cron:session): session closed for user root
Mar 14 16:04:01 raspberrypi CRON[26098]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 14 16:04:01 raspberrypi CRON[26099]: (root) CMD (/usr/sbin/omv-ionice >/dev/null 2>&1)
Mar 14 16:04:01 raspberrypi CRON[26098]: pam_unix(cron:session): session closed for user root
Mar 14 16:05:01 raspberrypi CRON[26108]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 14 16:05:01 raspberrypi CRON[26109]: (root) CMD (/usr/sbin/omv-ionice >/dev/null 2>&1)
Mar 14 16:05:01 raspberrypi CRON[26108]: pam_unix(cron:session): session closed for user root
Mar 14 16:06:01 raspberrypi CRON[26119]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 14 16:06:01 raspberrypi CRON[26120]: (root) CMD (/usr/sbin/omv-ionice >/dev/null 2>&1)
Mar 14 16:06:02 raspberrypi CRON[26119]: pam_unix(cron:session): session closed for user root
Mar 14 16:07:01 raspberrypi CRON[26129]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 14 16:07:01 raspberrypi CRON[26130]: (root) CMD (/usr/sbin/omv-ionice >/dev/null 2>&1)
Mar 14 16:07:01 raspberrypi CRON[26129]: pam_unix(cron:session): session closed for user root
Mar 14 16:08:01 raspberrypi CRON[26138]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 14 16:08:01 raspberrypi CRON[26139]: (root) CMD (/usr/sbin/omv-ionice >/dev/null 2>&1)
Mar 14 16:08:01 raspberrypi CRON[26138]: pam_unix(cron:session): session closed for user root
Mar 14 16:09:01 raspberrypi CRON[26148]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 14 16:09:01 raspberrypi CRON[26149]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 14 16:09:01 raspberrypi CRON[26151]: (root) CMD (/usr/sbin/omv-ionice >/dev/null 2>&1)
Mar 14 16:09:01 raspberrypi CRON[26150]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi)
Mar 14 16:09:01 raspberrypi CRON[26148]: pam_unix(cron:session): session closed for user root
Mar 14 16:09:01 raspberrypi CRON[26149]: pam_unix(cron:session): session closed for user root
Mar 14 16:09:08 raspberrypi systemd[1]: Starting Clean php session files...
Mar 14 16:09:09 raspberrypi systemd[1]: phpsessionclean.service: Succeeded.
Mar 14 16:09:09 raspberrypi systemd[1]: Finished Clean php session files.

Display More

Moreno · Mar 20th 2022

i will watch if the 425 log line is coming again before doing this, i think is a better idea no?

Posts by Moreno

applying modification on GUI after update

applying modification on GUI after update

applying modification on GUI after update

applying modification on GUI after update

applying modification on GUI after update

Errors were encountered while processing: docker-ce

Errors were encountered while processing: docker-ce

Errors were encountered while processing: docker-ce

Errors were encountered while processing: docker-ce

Errors were encountered while processing: docker-ce

Errors were encountered while processing: docker-ce

Errors were encountered while processing: docker-ce

Errors were encountered while processing: docker-ce

Errors were encountered while processing: docker-ce

Errors were encountered while processing: docker-ce

Folder2ram filesystem full

Folder2ram filesystem full

Folder2ram filesystem full

Folder2ram filesystem full

Folder2ram filesystem full