Cloudron Forum

@girish Yes it keeps crashing every day.

@girish Thank you, I have sent the email.

Hello, I am having a problem with updating Cloudron. At first, I found the system was not updating automatically at the scheduled time. So I start the update manually. After the backup, the Updating process was interrupted. In logs found:

Failed to start transient service unit: Unit cloudron-updater.service already exists.

So I kill the process and I repeat the updating process. After that, the updating process started, but there was no progress. In the logs, I found that there is a problem with grub:

Apr 24 17:56:41box:shell update (stdout): 2024-04-24T15:56:41 ==> update: cloudron-updater is still active. will check in 5 seconds
write error: Broken pipe
GRUB boot loader was previously installed to a disk that is no longer
or whose unique identifier has changed for some reason. It is important
make sure that the installed GRUB core image stays in sync with GRUB modules
grub.cfg. Please check again to make sure that GRUB is written to the
boot devices.
1. /dev/nvme1n1 (134217 MB; ) on 134217 MB Amazon Elastic Block Store
2. /dev/nvme2n1 (134217 MB; ) on 134217 MB Amazon Elastic Block Store
3. /dev/nvme0n1 (134217 MB; ) on 134217 MB Amazon Elastic Block Store
4. /dev/nvme0n1p15 (111 MB; /boot/efi) on 134217 MB Amazon Elastic Block Store
the items you want to select, separated by spaces.)
install devices:
of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111.
chose not to install GRUB to any devices. If you continue, the boot loader
not be properly configured, and when this computer next starts up it will
whatever was previously configured. If there is an earlier version of GRUB 2
the EFI system partition, it may be unable to load modules or handle the
configuration file.
you are already using a different boot loader and want to carry on doing so,
if this is a special environment where you do not need a boot loader, then
should continue anyway. Otherwise, you should install GRUB somewhere.
without installing GRUB? [yes/no]
of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111.
write error: Broken pipe
write error: Broken pipe
GRUB boot loader was previously installed to a disk that is no longer
or whose unique identifier has changed for some reason. It is important
make sure that the installed GRUB core image stays in sync with GRUB modules
grub.cfg. Please check again to make sure that GRUB is written to the
boot devices.
1. /dev/nvme1n1 (134217 MB; ) on 134217 MB Amazon Elastic Block Store
2. /dev/nvme2n1 (134217 MB; ) on 134217 MB Amazon Elastic Block Store
3. /dev/nvme0n1 (134217 MB; ) on 134217 MB Amazon Elastic Block Store
4. /dev/nvme0n1p15 (111 MB; /boot/efi) on 134217 MB Amazon Elastic Block Store
the items you want to select, separated by spaces.)
install devices:
of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111.
chose not to install GRUB to any devices. If you continue, the boot loader
not be properly configured, and when this computer next starts up it will
whatever was previously configured. If there is an earlier version of GRUB 2
the EFI system partition, it may be unable to load modules or handle the
configuration file.
you are already using a different boot loader and want to carry on doing so,
if this is a special environment where you do not need a boot loader, then
should continue anyway. Otherwise, you should install GRUB somewhere.
without installing GRUB? [yes/no]
of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111.
write error: Broken pipe
write error: Broken pipe
GRUB boot loader was previously installed to a disk that is no longer
or whose unique identifier has changed for some reason. It is important
make sure that the installed GRUB core image stays in sync with GRUB modules
grub.cfg. Please check again to make sure that GRUB is written to the
boot devices.
1. /dev/nvme1n1 (134217 MB; ) on 134217 MB Amazon Elastic Block Store
2. /dev/nvme2n1 (134217 MB; ) on 134217 MB Amazon Elastic Block Store
3. /dev/nvme0n1 (134217 MB; ) on 134217 MB Amazon Elastic Block Store
4. /dev/nvme0n1p15 (111 MB; /boot/efi) on 134217 MB Amazon Elastic Block Store
the items you want to select, separated by spaces.)
install devices:
of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111.
chose not to install GRUB to any devices. If you continue, the boot loader
not be properly configured, and when this computer next starts up it will
whatever was previously configured. If there is an earlier version of GRUB 2
the EFI system partition, it may be unable to load modules or handle the
configuration file.
you are already using a different boot loader and want to carry on doing so,
if this is a special environment where you do not need a boot loader, then
should continue anyway. Otherwise, you should install GRUB somewhere.
without installing GRUB? [yes/no]
of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111.
write error: Broken pipe
write error: Broken pipe
GRUB boot loader was previously installed to a disk that is no longer
or whose unique identifier has changed for some reason. It is important
make sure that the installed GRUB core image stays in sync with GRUB modules
grub.cfg. Please check again to make sure that GRUB is written to the
boot devices.
1. /dev/nvme1n1 (134217 MB; ) on 134217 MB Amazon Elastic Block Store
2. /dev/nvme2n1 (134217 MB; ) on 134217 MB Amazon Elastic Block Store
3. /dev/nvme0n1 (134217 MB; ) on 134217 MB Amazon Elastic Block Store
4. /dev/nvme0n1p15 (111 MB; /boot/efi) on 134217 MB Amazon Elastic Block Store
the items you want to select, separated by spaces.)
install devices:
of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111.
chose not to install GRUB to any devices. If you continue, the boot loader
not be properly configured, and when this computer next starts up it will
whatever was previously configured. If there is an earlier version of GRUB 2
the EFI system partition, it may be unable to load modules or handle the
configuration file.
you are already using a different boot loader and want to carry on doing so,
if this is a special environment where you do not need a boot loader, then
should continue anyway. Otherwise, you should install GRUB somewhere.
without installing GRUB? [yes/no]
of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111.
write error: Broken pipe
write error: Broken pipe
GRUB boot loader was previously installed to a disk that is no longer
or whose unique identifier has changed for some reason. It is important
make sure that the installed GRUB core image stays in sync with GRUB modules
grub.cfg. Please check again to make sure that GRUB is written to the
boot devices.
1. /dev/nvme1n1 (134217 MB; ) on 134217 MB Amazon Elastic Block Store
2. /dev/nvme2n1 (134217 MB; ) on 134217 MB Amazon Elastic Block Store
3. /dev/nvme0n1 (134217 MB; ) on 134217 MB Amazon Elastic Block Store
4. /dev/nvme0n1p15 (111 MB; /boot/efi) on 134217 MB Amazon Elastic Block Store
the items you want to select, separated by spaces.)
install devices:
of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111.
chose not to install GRUB to any devices. If you continue, the boot loader
not be properly configured, and when this computer next starts up it will
whatever was previously configured. If there is an earlier version of GRUB 2
the EFI system partition, it may be unable to load modules or handle the
configuration file.
you are already using a different boot loader and want to carry on doing so,
if this is a special environment where you do not need a boot loader, then
should continue anyway. Otherwise, you should install GRUB somewhere.
without installing GRUB? [yes/no]
of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111.
write error: Broken pipe
write error: Broken pipe
GRUB boot loader was previously installed to a disk that is no longer
or whose unique identifier has changed for some reason. It is important
make sure that the installed GRUB core image stays in sync with GRUB modules
grub.cfg. Please check again to make sure that GRUB is written to the
boot devices.
1. /dev/nvme1n1 (134217 MB; ) on 134217 MB Amazon Elastic Block Store
2. /dev/nvme2n1 (134217 MB; ) on 134217 MB Amazon Elastic Block Store
3. /dev/nvme0n1 (134217 MB; ) on 134217 MB Amazon Elastic Block Store
4. /dev/nvme0n1p15 (111 MB; /boot/efi) on 134217 MB Amazon Elastic Block Store
the items you want to select, separated by spaces.)
install devices:
of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111.
chose not to install GRUB to any devices. If you continue, the boot loader
not be properly configured, and when this computer next starts up it will
whatever was previously configured. If there is an earlier version of GRUB 2
the EFI system partition, it may be unable to load modules or handle the
configuration file.
you are already using a different boot loader and want to carry on doing so,
if this is a special environment where you do not need a boot loader, then
should continue anyway. Otherwise, you should install GRUB somewhere.
without installing GRUB? [yes/no]
of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111.
write error: Broken pipe

What should I do?

Thank you.

Thanks, it's solved. No disk wasn't changed. It's running on AWS.

Hello,
my Wordpress app is not responding. I assume that the error will be in the plugin. I am trying resolve it with WP CLI, but always I am getting something like this:

/usr/bin/wp: line 3: 22 Segmentation fault sudo -u www-data -i -- /app/pkg/wp --path=/app/data/public/ "$@"

Is this normal behavior?

@joseph Yes, I can't see it. It is WP multisite and its working..

@girish thank you after updating app package I can edit aliases