vicidial.org

Guys,

I think this version of REDUX 3.1.5 x64 have some bugs from install
scripts.

I tried many times to install it, and always get this at boot screen.

Code: Select all

Jan 14 11:51:43 vici udevd[431]: invalid KERNEL operation
Jan 14 11:51:43 vici udevd[431]: invalid rule '/etc/udev/rules.d/dahdi.rules:3'
Jan 14 11:51:43 vici udevd[431]: invalid KERNEL operation
Jan 14 11:51:43 vici udevd[431]: invalid rule '/etc/udev/rules.d/dahdi.rules:4'
Jan 14 11:51:43 vici udevd[431]: invalid KERNEL operation
Jan 14 11:51:43 vici udevd[431]: invalid rule '/etc/udev/rules.d/dahdi.rules:5'
Jan 14 11:51:43 vici udevd[431]: invalid KERNEL operation
Jan 14 11:51:43 vici udevd[431]: invalid rule '/etc/udev/rules.d/dahdi.rules:6'
Jan 14 11:51:43 vici udevd[431]: invalid KERNEL operation
Jan 14 11:51:43 vici udevd[431]: invalid rule '/etc/udev/rules.d/dahdi.rules:7'
Jan 14 11:51:43 vici udevd[431]: invalid KERNEL operation
Jan 14 11:51:43 vici udevd[431]: invalid rule '/etc/udev/rules.d/dahdi.rules:8'
Jan 14 11:51:43 vici udevd[431]: invalid SUBSYSTEM operation
Jan 14 11:51:43 vici udevd[431]: invalid rule '/etc/udev/rules.d/dahdi.rules:11'


Also is giving errors for some sangoma related error:

Code: Select all

Starting Sangoma wanrouter driver

ERROR: Wanpipe configuration file not found:
               /etc/wanpipe/wanpipe1.conf

Sangoma failed to load! Fallback to dahdi_dummy module!


and:

Code: Select all

mv: cannot stat `/var/log/asterisk/cdr-csv/Master.csv': No such file or directory
mv: cannot stat `/var/log/asterisk/cdr-custom/Master.csv': No such file or directory
rolling Asterisk screen log...
rolling Asterisk root screen log...
mv: cannot stat `/root/screenlog.0': No such file or directory
rolling Asterisk var log screen log...
mv: cannot stat `/var/log/asterisk/screenlog.0': No such file or directory



The last two are normal.

1) Attempt to use Sangoma timer, upon fail use dummy for timing. Perhaps it should be a notice instead of an ERROR, but I've gotten used to it.

2) Rolling logs when they don't exist yet is not surprising that it fails. I'm not sure it's worth building a system to detect that they don't exist yet and avoid showing this on the screen. But I'm sure if you pay for it ...

Then we have the invalid KERNEL operation ... that's an error. How/where did you experience this? If you tell the system that you do NOT have sangoma hardware at all, does this still occur?

I experienced the same Kernel errors on all my servers (in 3.1.3 and 3.1.4). Look at the beginning of this post: http://www.vicidial.org/VICIDIALforum/v ... hp?t=15252

It happens even when the system boots off the cd at the start of installation.

Actually it's happening from second step when doing Redux Install.

First step boots from Redux to begin install procedure.
Second step is after you take out install media and reboot.
Here appears this message on boot for first time...and so on every boot after.

Hmmm, I am pretty sure mine already happened when it first booted off the disk as well but I am speaking under correction.

Mine too

Vicibox 3.1.5 32 bit single server no hardware cards

please describe that again with "os-install" and "vicibox-install" as the stages ... so we know where you were.

The way I read it, you were experiencing this after the os-install? but before the vicibox-install?

As I said I am pretty sure I experienced this when the disk initially booted preparing for installation and upon every reboot thereafter. I hit esc to see behind the pretty Vicibox screen. Cannot verify 100% now because I am not at the office.

DarknessBBB, when do you see this error?

Trying wrote:DarknessBBB, when do you see this error?

I'm in your same situation, it is 8.48 pm here at 70% I remember to see the error at every reboot, even after the installation's end. Tomorrow I'll give it a reboot and we'll see...

That first error is udevd complaining about the way Digium wrote their udev rules. You can safely ignore it.

The second error is where the init script tries to load sangoma, but sangoma can't find any config/cards to load, so it falls back to the module specified, which is dahdi_dummy by default. This is normal and you can ignore it.

The third is where the init script does not find log files to roll. You can also safely ignore it.

so you are saying

Jan 14 11:51:43 vici udevd[431]: invalid KERNEL operation
Jan 14 11:51:43 vici udevd[431]: invalid rule '/etc/udev/rules.d/dahdi.rules:3'

will not result in loss of functionality, if there is a loss it is ... something else (although this error may be indicative of a specific version of the driver being installed which may have OTHER problems?)

If so ... where would the "other" problem become visible? Or would that be based on the "failure" being experienced? (such as the wanpipe driver not found, failing to dahdi_dummy, which is a bummer if you have installed the wanpipe driver ...?)

Digium rights most of their configs based on RedHat. sometimes if you are lucky there is a provision thrown in there for Ubuntu. Everyone else is kind of left to fend for themselves. It's just part of the territory.

interesting. so those of us from CentOS world will recognize the pathways (and the differences from our switch to SuSE)