Solved Message starting FreeBSD

Waldin

Waldin

Good Morning. For some time now, during the FreeBSD 13.1 system load, I have seen the following message:
Code: 
Waiting 3s for the default route interface: usage: procstat [--libxo] [-h] [-M core] [-N system] [-w interval] command
                [pid ... | core ...]
       procstat [--libxo] -a [-h] [-M core] [-N system]  [-w interval] command
       procstat [--libxo] [-h] [-M core] [-N system] [-w interval]
                [-S | -b | -c | -e | -f [-C] | -i [-n] | -j [-n] | -k [-k] |
                 -l | -r [-H] | -s | -t | -v | -x] [pid ... | core ...]
       procstat [--libxo] -a [-h] [-M core] [-N system] [-w interval]
                [-S | -b | -c | -e | -f [-C] | -i [-n] | -j [-n] | -k [-k] |
                 -l | -r [-H] | -s | -t | -v | -x]
       procstat [--libxo] -L [-h] [-M core] [-N system] core ...
Available commands:
       argument(s)
       auxv
       basic
       binary
       [cpuset | cs]
       credential(s)
       environment
       [fd(s) | file(s)] [-C]
       kstack [-v]
       pargs
                 -l | -r [-H] | -s | -t | -v | -x]
       procstat [--libxo] -L [-h] [-M core] [-N system] core ...
Available commands:
       argument(s)
       auxv
       basic
       binary
       [cpuset | cs]
       credential(s)
       environment
       [fd(s) | file(s)] [-C]
       kstack [-v]
       pargs
       penv
       ptlwpinfo
       pwdx
       rlimit
       rusage [-Ht]
       sigfastblock
       signal(s) [-n]
       thread(s)
       tsignal(s) [-n]
       vm

I don't know where to look to make it go away Any ideas? Thank you very much.
 
Hi!

Is this...
Thank you :)

Code: 
clear_tmp_enable="YES"
sshd_enable="NO"
background_dhclient="YES"
powerdxx_enable="YES"
powerdxx_flags="-a hiadaptive -b adaptive --max-batt 1900 -t dev.cpu.%d.temperature -N"
fanctl_enable="YES" 
sendmail_enable="NONE"
hostname="X200CA"
keymap="es.kbd"
ifconfig_alc0="DHCP"
ifconfig_alc0_ipv6="inet6 accept_rtadv"
wlans_ath0="wlan0"
ifconfig_wlan0="WPA DHCP powersave"
defaultroute_delay=3
defaultroute_carrier_delay=3
performance_cx_lowest="Cmax"
economy_cx_lowest="Cmax"
firewall_enable="YES"
firewall_quiet="YES"
firewall_type="client"
kld_list="i915kms"
moused_enable="YES"
ntpdate_enable="YES"
powerd_enable="NO"
# Set dumpdev to "AUTO" to enable crash dumps, "NO" to disable
dumpdev="NO"
dbus_enable="YES"
webcamd_enable="YES"
linux_enable="YES"
lightdm_enable="YES"
ifconfig_ue0="DHCP"
ubuntu_enable="YES"
 
Last edited by a moderator:
I'd remove this one:
Code: 
defaultroute_carrier_delay=3

What's this one supposed to do?
Code: 
ubuntu_enable="YES"
 
Thanks for your help.

I had already tried to comment the line defaultroute_carrier_delay=3 in rc.conf with no result.
Regarding ubuntu_enable="YES" is that I have followed the instructions to get Linux Brave browser working on FreeBSD 13.0+

Linux Brave browser on FreeBSD 13+
 
I'm fairly sure that's where the error is coming from. Not sure exactly where though, but just test it, remark the ubuntu_enable and reboot. If the error is gone you know where to look further.
 
Hi!
Commenting the line ubuntu_enable not change anything. The message continues...

Maybe it's a bug in the script that needs to be created in /usr/local/etc/rc.d/ubuntu for the Brave browser to work.
 
Not really, you should type linux_enable="NO", and l leave ubuntu_enable="YES", but this is not concern about your issue, report your /etc/fstab about ubuntu chroot: that should be like in this thread [Linuxulator] How to run Google Chrome (linux-binary) on FreeBSD just change where is typed linux with ubuntu, example: linprocfs /compat/ubuntu/proc linprocfs instead of /compat/linux.If you are some other issue just check this [Linuxulator] How to install Brave (Linux app) on FreeBSD 13.0+ or this one Install Ubuntu base system into FreeBSD’s Linux Binary Compatibility by the author of github script to autoconfigure the system.
Remenber to put linux_mounts_enable="NO".About procstat utility maybe you have script to check during boot sequence this infos and this is misconfigured this is the manual reference page FreeBSD Manual Pages :) Good Luck. P.S.:maybe is the firewall check the ruleset
 
Hi!
Well, I can't find the solution. I have put in rc.conf:
linux_enable="NO"
ubuntu_enable="NO"

And the message persists. I understand then that it has nothing to do with the compatibility with linux, since it is deactivated. Looking with dmesg -a | more, the message appears after the line: Updating /var/run/os-release done.
 
Why is it showing alc0 and wlan0 when the rc.conf you posted earlier has no mention of it?

Edit: That appears to be my mistake. You posted a file and I copy/pasted that in a [code]..[/code] block. Somehow I only copied half the content.
 
This:
Code: 
Waiting 3s for the default route interface: usage: procstat [--libxo] [-h] [-M core] [-N system] [-w interval] command
                [pid ... | core ...]
       procstat [--libxo] -a [-h] [-M core] [-N system]  [-w interval] command
       procstat [--libxo] [-h] [-M core] [-N system] [-w interval]
                [-S | -b | -c | -e | -f [-C] | -i [-n] | -j [-n] | -k [-k] |
                 -l | -r [-H] | -s | -t | -v | -x] [pid ... | core ...]
       procstat [--libxo] -a [-h] [-M core] [-N system] [-w interval]
                [-S | -b | -c | -e | -f [-C] | -i [-n] | -j [-n] | -k [-k] |
                 -l | -r [-H] | -s | -t | -v | -x]
       procstat [--libxo] -L [-h] [-M core] [-N system] core ...
Available commands:
       argument(s)
       auxv
       basic
       binary
       [cpuset | cs]
       credential(s)
       environment
       [fd(s) | file(s)] [-C]
       kstack [-v]
       pargs
       penv
       ptlwpinfo
       pwdx
       rlimit
       rusage [-Ht]
       sigfastblock
       signal(s) [-n]
       thread(s)
       tsignal(s) [-n]
       vm
(wlan0)
add host 127.0.0.1: gateway lo0 fib 0: route already in table
add host ::1: gateway lo0 fib 0: route already in table
add net fe80::: gateway ::1 fib 0: route already in table
add net ff02::: gateway ::1 fib 0: route already in table
add net ::ffff:0.0.0.0: gateway ::1 fib 0: route already in table
add net ::0.0.0.0: gateway ::1 fib 0: route already in table
Appears to be happening while configuring the wlan0 interface.

What happens if you remove the powersave here:
Code: 
ifconfig_wlan0="WPA DHCP powersave"

Can you also post your /etc/wpa_supplicant.conf? You can obfuscate your actual SSID and password of course.
 
SirDice said:
Appears to be happening while configuring the wlan0 interface.
Click to expand...

Not necessarily. For example, I have on my system in dmesg(8) (same in /var/log/messages) two messages which get intermingled:

Rich (BB code): 
pcm0: <ATI R6xx (HDMI)>GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI:     Crypto: accelerated software
 at nid 3 on hdaa0

It should be:
Code: 
pcm0: <ATI R6xx (HDMI)> at nid 3 on hdaa0
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI:     Crypto: accelerated software

It's possible we see here the same. The procstat(1) error message might be printed in between Waiting 3s for the default route interface: (wlan0)

I was hoping verbose boot giving a hint.

Waldin, please disable (comment) following variables in /etc/rc.conf and reboot system:
Code: 
background_dhclient="YES"
ifconfig_alc0="DHCP"
ifconfig_alc0_ipv6="inet6 accept_rtadv"
wlans_ath0="wlan0"
ifconfig_wlan0="WPA DHCP powersave"
defaultroute_delay=3
defaultroute_carrier_delay=3

Let's see if procstat(1) error still gets printed. If it does then we need to look elsewhere.
 
Hello. Commenting on these lines, logically leaves my computer without an Internet connection, and after the test, I had to activate them to be able to respond.

Attached the file with the result of dmesg -a new and wpa_supplicant.conf

The message continues. Now after Starting syslogd

Thanks
 

Attachments

  • boot.txt
    68 KB · Views: 64
  • wpa_supplicant.conf
    212 bytes · Views: 55
Sounds like you might have to clean out everything in /etc/rc.conf and then add things one line at a time until you find the culprit.

Obviously you'll need to put them all back in to have a functioning system, but to try and track down what is causing it you might have start with as little as possible/nothing.
 
Hello. I can confirm that the error is not in the /etc/rc.conf file. I have deleted it (previous backup) and the message keeps appearing... I'm going crazy, but I'll keep digging. Thank you all for trying to help me.
 
Waldin said:
Good Morning. For some time now, during the FreeBSD 13.1 system load, I have seen the following message:
Code: 
Waiting 3s for the default route interface: usage: procstat [--libxo] [-h] [-M core] [-N system] [-w interval] command
                [pid ... | core ...]
       procstat [--libxo] -a [-h] [-M core] [-N system]  [-w interval] command
       procstat [--libxo] [-h] [-M core] [-N system] [-w interval]
                [-S | -b | -c | -e | -f [-C] | -i [-n] | -j [-n] | -k [-k] |
                 -l | -r [-H] | -s | -t | -v | -x] [pid ... | core ...]
       procstat [--libxo] -a [-h] [-M core] [-N system] [-w interval]
                [-S | -b | -c | -e | -f [-C] | -i [-n] | -j [-n] | -k [-k] |
                 -l | -r [-H] | -s | -t | -v | -x]
       procstat [--libxo] -L [-h] [-M core] [-N system] core ...
Available commands:
       argument(s)
       auxv
       basic
       binary
       [cpuset | cs]
       credential(s)
       environment
       [fd(s) | file(s)] [-C]
       kstack [-v]
       pargs
                 -l | -r [-H] | -s | -t | -v | -x]
       procstat [--libxo] -L [-h] [-M core] [-N system] core ...
Available commands:
       argument(s)
       auxv
       basic
       binary
       [cpuset | cs]
       credential(s)
       environment
       [fd(s) | file(s)] [-C]
       kstack [-v]
       pargs
       penv
       ptlwpinfo
       pwdx
       rlimit
       rusage [-Ht]
       sigfastblock
       signal(s) [-n]
       thread(s)
       tsignal(s) [-n]
       vm

I don't know where to look to make it go away Any ideas? Thank you very much.
Click to expand...

It seems to be an error in the syntax of the init script
Code: 
usage
this line tell me this
try to replace(before backup the file) /etc/rc.d/defaultroute for another one from a fresh instalation
 
SirDice said:
Did you perhaps put something in /etc/rc.local?
Click to expand...

Sounds quite likely. Or something there might call procstat indirectly, definitely worth checking.

T-Daemon said:
Try also as root grep -r procstat /etc /usr/local/etc /var/cron .
Click to expand...

If that doesn't find it, it may not be easy to find. Certainly not in anything linux it seems.

I've downloaded both dmesg and tried to spot where the procstat usage message occurs against seeing it from /etc/rc's point of view, ie rcorder(8)

# sh -c 'rcorder /etc/rc.d/* 2>/dev/null'

I'm on 12.3 so won't quote mine, likely a few differences, but generally one can correlate dmesg logs with that order of processes.

And yes, verbose messages could well provide more clues than normal (brief) logging.

T'were me, I'd add both
Code: 
boot_verbose="YES"
verbose_loading="YES"
to /boot/loader.conf until this was sorted out.
 
wolffnx said:
It seems to be an error in the syntax of the init script
Code: 
usage
this line tell me this
try to replace(before backup the file) /etc/rc.d/defaultroute for another one from a fresh instalation
Click to expand...
Sorry, but I don't have another computer to do a fresh install...
 
You must log in or register to reply here.
Back
Top