Update error: Another instance is already running... Aborting!
-
When trying to update via the web gui I get the error "unable to check for updates"
When using the CLI running: pkg-static update -f
I get:
Updating pfSense-core repository catalogue... Fetching meta.conf: 100% 163 B 0.2kB/s 00:01 Fetching packagesite.pkg: 100% 2 KiB 1.7kB/s 00:01 Processing entries: 100% pfSense-core repository update completed. 7 packages processed. Updating pfSense repository catalogue... Fetching meta.conf: 100% 163 B 0.2kB/s 00:01 Fetching packagesite.pkg: 100% 149 KiB 152.9kB/s 00:01 Processing entries: 0% Newer FreeBSD version for package pfSense-pkg-node_exporter: To ignore this error set IGNORE_OSVERSION=yes - package: 1203500 - running kernel: 1202504 Ignore the mismatch and continue? [y/N]: y Processing entries: 100% pfSense repository update completed. 511 packages processed. All repositories are up to date.
After CLI running: pfSense-upgrade -d -c
Another instance is already running... Aborting!
Switching DNS servers does't make a difference...
any thoughts on how to troubleshoot?
-
@helloha said in Update error: Another instance is already running... Aborting!:
any thoughts on how to troubleshoot?
If you have the impression that the already running upgrade instance doesn't work, is stalled, kill it.
@helloha said in Update error: Another instance is already running... Aborting!:
When using the CLI running:
ps ax | grep 'pkg'
and see what's running. use the pid to kill it if needed.
-
@gertjan thx for reply. It doesn't work. It is also persistent during reboots...
[2.5.2-RELEASE][root@pfSense.xxx.be]/root: ps ax | grep 'pkg' 14712 - I 0:00.00 pkg-static update 14819 - I 0:00.02 pkg-static update 89314 0 S+ 0:00.00 grep pkg [2.5.2-RELEASE][root@pfSense.xxx.be]/root: pfSense-upgrade -d -c Another instance is already running... Aborting! [2.5.2-RELEASE][root@pfSense.xxx.be]/root:
-
If you have tow instances "pkg-static" running.
"pfSense-upgrade" uses "pkg-static".So, again, if they seem to 'do not', kill them.
kill 14712 kill 14819
And try again.
Btw : do a local resolver test like
dig google.com +short
You should get back an IPv4.
-