# pakfire info wio
Name: wio
Summary: Who Is Online? IPFire extension
Version: 1.3.2-19
Size: 70.00 KB
Dependencies:
Pakfile: wio-1.3.2-19.ipfire
Service InitScripts:
Installed: yes
Status: up-to-date
There was a noticeably connectivity failure at my ISP infrastructure today so I decided to configure WIO to monitor situation. It is new WIO config, C203.
I cannot see graphs and when I click “Update Client Now”, there is an error but it is not well visible and it is visible only for a second. After several tries I was able to capture the error:
Error in RRD::create for Who Is Online: Cannot create temporary file
Errors are in /var/log/messages too:
Aug 4 03:00:03 ipfire wio: opening '/var/log/rrd/wio/5.rrd': No such file or directory
Aug 4 03:00:03 ipfire wio: opening '/var/log/rrd/wio/3.rrd': No such file or directory
Aug 4 03:00:03 ipfire wio: opening '/var/log/rrd/wio/2.rrd': No such file or directory
Aug 4 03:00:03 ipfire wio: opening '/var/log/rrd/wio/6.rrd': No such file or directory
Aug 4 03:00:03 ipfire wio: opening '/var/log/rrd/wio/1.rrd': No such file or directory
Aug 4 03:00:03 ipfire wio: opening '/var/log/rrd/wio/4.rrd': No such file or directory
wio directory is missing:
[root@ipfire ~]# ls -ltr /var/log/rrd/
total 68
drwxr-xr-x 3 root root 4096 Jul 12 23:23 collectd
-rw-r--r-- 1 root root 28728 Aug 4 03:00 hddshutdown-sda.rrd
-rw-r--r-- 1 root root 28728 Aug 4 03:00 hddtemp-sda.rrd
The extraction of the wio addon package creates the /var/log/wio and /var/log/wio/wioips directories and then sets the owner of those directories to nobody:nobody. It also creates the directory /var/log/rrd/wio
As you don’t have the directories in place then something must have gone wrong during the installation process.
Please provide the contents of /var/log/pakfire/install-wio.log and do you have the directory /var/log/wio present on your system?
removed '/usr/lib/security/pam_cap.so'
useradd warning: knot-resolver's uid 120 outside of the UID_MIN 1000 and UID_MAX 60000 range.
Extracting files...
./
var/
var/spool/
var/spool/dma/
var/spool/cron/
var/spool/cron/root.orig
var/spool/cron/new.root
var/log/
var/log/updatexlrator/
var/log/squid/
var/log/squid/access.log
var/log/rrd/
var/log/rrd/wio/
var/log/pakfire/
var/log/openvpn/
var/lib/
...
2026-07-21 20:11:52 INFO reinstalling root's fcrontab
2026-07-21 20:11:52 INFO installing file /tmp/fcr-hn8VCS for user root
Modifications will be taken into account right now.
Profile was not sent propertly: [Errno -2] Name or service not known
dracut[I]: Executing: /usr/bin/dracut --kver=6.18.32-ipfire --force
dracut[I]: *** Including module: modsign ***
dracut[I]: *** Including module: i18n ***
No such file or directory.
URL: http+unix://%2Frun%2Fknot-resolver%2Fkres-api.sock/reload
Host/Path: /run/knot-resolver/kres-api.sock
Sourced from: Default value "/run/knot-resolver/kres-api.sock"
Is the URL correct?
Unix socket would start with http+unix:// and URL encoded path.
Inet sockets would start with http:// and domain or ip
dracut[I]: *** Including module: btrfs ***
dracut[I]: *** Including module: dm ***
dracut[I]: *** Including module: fs-lib ***
...
Just an idea, could process that keeps /var/log directory clean remove /var/log/rrd/wio directory because it was not updated for several days (wio was not enabled)?
The last pasted section has nothing to do with WIO.
It also gets resolved quickly during the reboot so it is nothing blocking anything.
The install log shows
So the ```/var/log/rrd/wio/```` directory was created and there is no error message indicating that it could not be created, so it must have been created and then after the install was comp0leted, it must have been removed.
In the update section it did not remove the /var/log/rrd/wio/ directory as it wasn’t present but then the install showed it extracting the directory again.
If after the install sections the /var/log/rrd/wio directory is not present then it can only be because of something like the permissions of the directory tree being incorrect.
You didn’t answer the question if /var/log/wio/ is present on your system?
If it is then the issue is specifically with the /var/log/rrd/ directory tree. If that directory is not present then the issue is more likely with the /var/log/ directory tree.
The upgrade to C203 was not an easy task on this gateway. DNS was configured to “TLS” and after reboot, DNS was down (because DNS hostnames were empty), plugins were not updated (pakfire was not able to connect to the repository). I updated plugins later, once I changed DNS from TLS to UDP… I am not sure if this is important but I just write it here, maybe this was the trigger for the trouble with wio.
If you uninstall wio and then install it again, is the ```/var/log/rrd/wio/```` directory present or is it still missing.
That would show if there was some hiccup during the update process due to the issues you had that prevented the directory creation or if it is a consistent issue with wio on CU203..
I can’t test out a fresh install of wio at the moment as the system I use for the vm testbed has been disconnected while a network cable update is occurring.
I should be finished by Wed or Thurs so will do some testing of a fresh wio install at that time and see if I can reproduce a missing /var/log/rrd/wio/ directory.
My wio update from CU202 to CU203 did not have any problem but the /var/log/rrd/wio/ directory was already there in CU203 and much earlier.
I have not uninstall anything. I just upgraded C201 C202 to C203 and after reboot there was no DNS. Plugins were not updated before reboot and it was no possible to update anything until I fixed DNS…
I am asking you, on your CU203 system, to go to the WUI pakfire page and uninstall wio. Then when that has completed, use the WUI pakfire page to install wio again.
Then check if the /var/log/rrd/wio/ directory is present there or not.
There is a bug! I disabled “wio”, I wanted to do uninstall and install of wio. File /var/log/wio/wioips was “erased” it has size 0, all clients configuration was lost. I only “disabled wio service”.
[root@ipfire ~]# ls -ltr /var/log/wio/wioips
-rw-r--r-- 1 nobody nobody 0 Aug 4 14:55 /var/log/wio/wioips
I have backup of that file so I can restore it but I am surprised with such behavior, it is a bug… I have not uninstalled the wio yet, I was preparing for that step and wio erased host DB by just disabling the service.
Update, it looks like file is erased again and again, I see that timestamp is updating (no action from my side, I just watch):
[root@ipfire ~]# ls -ltr /var/log/wio/wioips
-rw-r--r-- 1 nobody nobody 0 Aug 4 15:00 /var/log/wio/wioips
There is a warning dialog when I unselect the enable checkbox. I think I missed it or it was not there…
Attention! It will reset all settings including the client to be checked!
I cannot find any way to backup or restore list of wio clients from GUI…
When file /var/log/wio/wioips is missing, wio.cgi page ends with an internal error. Missing file or directory is not created by wio.cgi.
@pslpsl .
It is really difficult to reproduce your error.
Nobody knows the state of your system, nobody knows the process of updating wio on your system.
Therefore you should do the steps @bonnietwin supposed. This is a reproducible process, which functions on most systems.
If it doesn’t succeed we can look at the problems occuring, and define a bug for a system with your conditions and config.
[root@ipfire ~]# ls -ltrd /var/log/{wio,rrd/wio}
ls: cannot access '/var/log/wio': No such file or directory
ls: cannot access '/var/log/rrd/wio': No such file or directory
