APU2 23.05.1-RELEASE to 23.09. failed
-
Update failed, APU 2 no response;
How to get 23.05.1-RELEASE für APU2 for re-install?
br hsrtreml
-
How did it fail? What is it doing now?
You can install 2.7.1 and then upgrade to 23.09 if your sub is current, which it probably is.
Steve
-
@stephenw10 Hi stephenw, thnaks, but this is not my solution
- i need 23.05.1 back, so i can restore my config file.
or you have some ideas for that:
ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib /usr/local/lib/compat/pkg /usr/lib/engines /usr/local/lib/compat/pkg /usr/local/lib/freeradius-3.2.2 /usr/locE
ldconfig: mkstemp(/var/run/ld-elf.so.hints.daQGs8): No such file or directory
assword:2023-12-02T09:26:34.176449+01:00 - apcupsd 154 - - Communications with UPS lost.
ldconfig: mkstemp(/var/run/ld-elf32.so.hints.sPTBci): No such file or directory
Starting devd.
devd: bind: No such file or directory
/etc/rc: WARNING: failed to start devd
ld-elf.so.1: Shared object "libintl.so.8" not found, required by "libpython3.11.so.1.0"
Updating motd:install: /var/run/motd: No such file or directory
.
eval: cannot create /var/run/dmesg.boot: No such file or directory
Updating /var/run/os-release install: /var/run/os-release: No such file or directory
done.
Creating and/or trimming log files.
eval: cannot create /var/run/syslogd.sockets: No such file or directory
Starting syslogd.
syslogd: cannot open pid file: No such file or directory
protect: option requires an argument -- p
usage: protect [-i] command
protect [-cdi] -g pgrp | -p pid
/etc/rc: WARNING: Dump directory does not exist. Savecore not run.
/etc/rc: WARNING: $timed_enable is not set properly - see rc.conf(5).
Mounting late filesystems:.
Starting cron.
cron: can't open or create /var/run/cron.pid: No such file or directory
/etc/rc: WARNING: failed to start cron
/etc/rc: WARNING: $sshguard_enable is not set properly - see rc.conf(5).
/etc/rc: WARNING: $scponlyc_enable is not set properly - see rc.conf(5).
Starting background file system checks in 60 seconds. -
And nothing after that?
Looks like it partially upgraded with the library errors.
You can recover a 23.05.1 config in to 23.09.
-
@stephenw10 thanks for your support again; but ...
now th apu2 is from 2.71 to 23.09
to restoring the config-file from 23.05.1 is not possible (internal config number is 22.9)...
-
You can restore a 22.9 config into 2.7.1 or 23.09. In general you can always restore an older config into a newer pfSense version.
