Messages

331

Feature requests & roadmap / Re: Monitoring

« on: January 19, 2012, 07:35:00 am »

I'm not sure that i understand what you're saying here.
You mean that you've got a syslog server already in place?
Is there somewhere a wiki about this? The most part i'm interested in, is the ease to view it. The GUI to say it like that...


ps I'm not trying to implement "other" things. I'm just a big fan of the cacti architecture because it's really fast, complete monitoring/alerting tool, and above all: it's awonderful and  'idiot prove' GUI... And this last part has been proven several times in my professional live...
Monitoring presence, graph bandwidth-load-..., alerting, nicely view all your logs, weathermaps, inventory your network... With all this,  it's just your imagination that blocks you... So it's not only the log module, it's the combination of it all...
Fe i receive a mail once my power usuage is going above 5000W, or a mail is send out once my HD is about 75% full. And all this without scripting (or at least without the knowledge of scripting)...
For me, it's just a big + to have something like this added to 'my' central server that already controls everything...
Send me a PM if you want to log in to my server with a bit more user credentials. So you can see what else we (=linuxmce users) could do with this tool...

332

Users / Re: Improving network proformance

« on: January 19, 2012, 07:19:59 am »

Start first with some local tests. Check your collisions and so. This can help you to find out if you've got a cable issue, poor networkcard...
See my original post above...

Always work the layers up!!!
It's a very good and proven troubleshooting path...

333

Users / Re: Appearing/Disappearing Hard Drives

« on: January 19, 2012, 07:14:50 am »

Please understand fellas, the hard drives are mounted AS NEEDED by autofs. The UpdateMedia system understands this, and it continually scans the connected filesystems, so you'll see the disks periodically mount and unmount.
-Thom

Explains a lot. No, wait. Explains everything...

At least for my situation...
Thanks!

334

Users / Re: Improving network proformance

« on: January 18, 2012, 11:04:44 am »

First of all, try to understand (draw) your connection. What's your WAN interface, what's your LAN interface (fe in my case is LAN: eth0, WAN: eth1). This way you know where you're looking. A picture is saying a lot more then some words.

I'll put some basic test here that can point you to the right place where to look...


Connect
Can you connect with ssh to your core? I'll assume you're using a linux client.

Code: [Select]

ssh username@192.168.80.1

Network interfaces
With ifconfig, you'll see a lot more about your network cards.

Code: [Select]

ifconfig-> do you see any errors on the interfaces (collisions)? In fact, you should only see RX/TX packets here...
-> What the subnetmask of you interfaces (the same as for your routing table)?

fe

eth0      Link encap:Ethernet  HWaddr 00:21:85:5d:d6:05  
          inet addr:192.168.80.1  Bcast:192.168.80.255  Mask:255.255.255.0
          inet6 addr: fe80::221:85ff:fe5d:d605/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:4338750 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2156345 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1817464938 (1.8 GB)  TX bytes:161459655 (161.4 MB)
          Interrupt:219 Base address:0xa000

eth1      Link encap:Ethernet  HWaddr 00:04:76:97:7b:98  
          inet addr:192.168.0.184  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::204:76ff:fe97:7b98/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:49496 errors:0 dropped:0 overruns:0 frame:0
          TX packets:32634 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:26781428 (26.7 MB)  TX bytes:7483598 (7.4 MB)
          Interrupt:21 Base address:0xac00

For more information, you can always do following:

Code: [Select]

sudo ethtool -S eth0This should give you more information:

NIC statistics:
     tx_packets: 2190314
     rx_packets: 4367767
    tx_errors: 0
     rx_errors: 0
     rx_missed: 0
     align_errors: 1166
     tx_single_collisions: 0
     tx_multi_collisions: 0
     unicast: 4350464
     broadcast: 11762
     multicast: 5541
     tx_aborted: 0
     tx_underrun: 0

Routing

Code: [Select]

netstat -rn-> should give you a clear routing table

fe

192.168.0.0     0.0.0.0         255.255.255.0  U         0 0          0 eth1 <<<Your WAN network>>>
192.168.80.0   0.0.0.0         255.255.255.0   U         0 0          0 eth0 <<<Your LAN network>>>
0.0.0.0        192.168.0.1    0.0.0.0         UG        0 0          0 eth1 <<<All the rest to your internetprovider>>>

Traceroute
With a traceroute you'll see the connection path. This is useful to see where your connections goes, and if any devices are taking a long time to respond.
This is best done from you client machine on (i don't have direct access to a client now, so i can't show you my result, sorry).

Code: [Select]

traceroute linuxmce.org
fe (this is done from another network, so it won't be the same for you). The most important thing in here are the first lines, with your private ip's, and the first public ip (your internetrouter):

traceroute to linuxmce.org (193.200.113.133), 30 hops max, 60 byte packets
1  192.168.80.1 (192.168.80.1)  3.575 ms  3.778 ms  4.355 ms <<< Your internal gateway >>>
 2  192.168.0.1 (172.31.31.1)  7.338 ms  7.716 ms  7.932 ms <<< Your internet gateway >>>
 3  3.123-123-109.adsl-dyn.isp.belgacom.be (109.123.123.3)  14.416 ms  16.522 ms  19.280 ms  <<< Your public ip >>>
 4  160.241-183-91.adsl-static.isp.belgacom.be (91.183.241.160)  21.939 ms  24.110 ms  26.778 ms
 5  ae-15-1000.ibrstr1.isp.belgacom.be (91.183.246.107)  52.974 ms  31.339 ms  53.332 ms
 6  bru-11-r6-t9-4.car.belbone.be (80.84.20.18)  36.676 ms bru-11-r6-t8-4.car.belbone.be (80.84.20.78)  13.732 ms bru-11-r6-t7-4.car.belbone.be (80.84.21.34)  14.288 ms
 7  94.102.162.50 (94.102.162.50)  17.156 ms  19.748 ms  22.358 ms
 8  neotelecoms.bnix.net (194.53.172.79)  31.315 ms  33.714 ms  36.135 ms
 9  xe0-0-0.tcr1.gs.par.as8218.eu (83.167.55.20)  58.078 ms  58.461 ms  58.842 ms
10  83.167.56.155 (83.167.56.155)  62.023 ms  64.715 ms  67.321 ms
11  xe0-1-1.r06.uni.vie.at.nextlayer.net (212.69.191.150)  67.712 ms  69.814 ms  35.678 ms
12  xe4-1-1.r05.rdh.vie.at.nextlayer.net (92.60.3.144)  38.981 ms xe2-1-0.r05.rdh.vie.at.nextlayer.net (92.60.2.144)  39.179 ms xe4-1-1.r05.rdh.vie.at.nextlayer.net (92.60.3.144)  40.699 ms
13  vl21.r02.rdh.vie.at.nextlayer.net (81.16.147.192)  43.634 ms  45.582 ms  50.315 ms
14  abaton.rdh.vie.at.nextlayer.net (81.16.148.34)  51.541 ms  37.767 ms  39.880 ms
15  193.200.112.37 (193.200.112.37)  41.829 ms  43.772 ms  45.978 ms
16  94.247.144.120 (94.247.144.120)  48.424 ms  50.878 ms  53.792 ms
17  193.200.113.133 (193.200.113.133)  55.457 ms  35.938 ms  38.298 ms

Send us the results of this, from there on we can maybe start troubleshoot a bit more ...

Of course, it's best that you do all this tests from all the machines (or at least all the machines that are in the loop). This is the reason why i wrote that's always best to have a small drawing beside... This way, you can isolate the problem to  a certain point/connection...

335

Users / Re: Appearing/Disappearing Hard Drives

« on: January 18, 2012, 10:37:10 am »

Hey,

I noticed a bit the same when I added a 1TB to my system.
My monitoring sees the disk mostly as 'down', and from time to time it was there.

For the moment I removed it again since i didn't trust the situation...
So I certainly will follow up this topic for the results...  

336

Users / All network nodes

« on: January 18, 2012, 08:14:52 am »

I'm wondering if it's useful to add all your nodes to the core. Things like printers, workstations, wireless access points... Today i'm suffering some 'human' issues with this.

My home network runs in another domain then the core router. So when i browse my network, i see different domains. And not all my nodes have a nice dns name.
I tried to put them with webmin in the DNS and so. But when i reboot the core, it retake the dcerouter name and pluto domain. 
I already added a lot of stuff into dhcpd-extra, but this isn't added in my normal domain.

Okay, i hear you saying to change my 'home domain', but i want to avoid this since a lot of maps/scripts/... are running with this. So i'm thinking now to add all devices as 'child devices' in the core?

I'm just wondering how you guys solve this situations...

337

Installation issues / Re: Asterisk Manager Connection Failure

« on: January 17, 2012, 03:06:24 pm »

I tried to remove and reinstall freepbx (since not a lot of config is done for the moment), but the end result stays the same...

Code: [Select]

dpkg -r --force-all freepbx
apt-get install freepbx

btw: The version is now " FreePBX 2.3.1.0 "

338

Installation issues / Asterisk Manager Connection Failure

« on: January 17, 2012, 01:44:11 pm »

I'm playing around with the phone section.
I started in freepbx to add some phones and so, everything was working. And after that, i started to learn about how it should be done. Not directly adding the phone in freepbx, but through linuxmce. So i removed the extensions, started to add my phones by linuxmce... And i did somewhere a module update within asterisk...
But now, freepbx won't start anymore.

When i try to 'reload the changed configuration', i get:

Code: [Select]

exit: 1
Checking for PEAR DB..OK
Checking for PEAR Console::Getopt..OK
Checking for /etc/amportal.conf ..OK
Bootstrapping /etc/amportal.conf ..OK
Parsing /etc/amportal.conf ..OK
Parsing /etc/asterisk/asterisk.conf ..OK
Connecting to database..OK
Connecting to Asterisk manager interface..FAILED
[FATAL] Asterisk Manager Connection Failure Failed to connect to the Asterisk manager through port: 5038

1 error(s) occured, you should view the notification log on the dashboard or main screen to check for more details.
Maybe some additional logs (/var/log/asterisk/full):

Code: [Select]

[Jan 17 13:55:27] NOTICE[31247] cdr.c: CDR simple logging enabled.
[Jan 17 13:55:27] NOTICE[31247] loader.c: 166 modules will be loaded.
[Jan 17 13:55:27] WARNING[31247] loader.c: Error loading module 'format_au.so': /usr/lib/asterisk/modules/format_au.so: cannot
 open shared object file: No such file or directory
[Jan 17 13:55:27] WARNING[31247] loader.c: Error loading module 'format_mp3.so': /usr/lib/asterisk/modules/format_mp3.so: cann
ot open shared object file: No such file or directory
[Jan 17 13:55:27] WARNING[31247] res_musiconhold.c: Cannot open dir /var/lib/asterisk/mohmp3/none/ or dir does not exist
[Jan 17 13:55:27] WARNING[31247] res_config_pgsql.c: Unable to load config res_pgsql.conf
[Jan 17 13:55:27] NOTICE[31247] res_smdi.c: Unable to load config smdi.conf: SMDI disabled
[Jan 17 13:55:27] WARNING[31247] res_smdi.c: No SMDI interfaces are available to listen on, not starting SMDI listener.
[Jan 17 13:55:27] WARNING[31247] res_odbc.c: Unable to load config file res_odbc.conf
[Jan 17 13:55:27] WARNING[31247] res_jabber.c: No such configuration file jabber.conf
[Jan 17 13:55:27] ERROR[31247] res_jabber.c: JABBER: Failed to load config.
[Jan 17 13:55:27] NOTICE[31247] config.c: Registered Config Engine odbc
[Jan 17 13:55:27] WARNING[31247] res_snmp.c: Could not load res_snmp.conf
[Jan 17 13:55:27] WARNING[31247] loader.c: Error loading module 'format_au.so': /usr/lib/asterisk/modules/format_au.so: cannot
 open shared object file: No such file or directory
[Jan 17 13:55:27] WARNING[31247] loader.c: Module 'format_au.so' could not be loaded.
[Jan 17 13:55:27] WARNING[31247] loader.c: Error loading module 'format_mp3.so': /usr/lib/asterisk/modules/format_mp3.so: cann
ot open shared object file: No such file or directory
[Jan 17 13:55:27] WARNING[31247] loader.c: Module 'format_mp3.so' could not be loaded.
[Jan 17 13:55:27] WARNING[31247] cdr_addon_mysql.c: MySQL database sock file not specified.  Using default
[Jan 17 13:55:27] NOTICE[31247] cdr_addon_mysql.c: MySQL database table not specified.  Assuming "cdr"
[Jan 17 13:55:27] WARNING[31247] chan_sip.c: tos value at line 20 is deprecated.  See doc/ip-tos.txt for more information.
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot disallow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot allow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot disallow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot allow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot disallow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot allow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot disallow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot allow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot disallow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot allow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot disallow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot allow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot disallow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot allow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot disallow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot allow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot disallow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot allow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot disallow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot allow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot disallow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot allow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot disallow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot allow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot disallow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot allow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot disallow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot allow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot disallow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot allow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot disallow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot allow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot disallow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot allow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot disallow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot allow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot disallow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot allow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot disallow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot allow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot disallow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot allow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot disallow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot allow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot disallow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot allow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot disallow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot allow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot disallow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot allow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot disallow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot allow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot disallow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot allow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot disallow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot allow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot disallow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot allow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot disallow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot allow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot disallow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot allow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot disallow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot allow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot disallow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot allow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot disallow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot allow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot disallow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot allow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot disallow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot allow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot disallow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot allow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot disallow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot allow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot disallow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot allow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot disallow unknown format ''
[Jan 17 13:55:27] WARNING[31247] frame.c: Cannot allow unknown format ''
[Jan 17 13:55:27] WARNING[31247] pbx_config.c: The use of '_.' for an extension is strongly discouraged and can have unexpecte
d behavior.  Please use '_X.' instead at line 59
[Jan 17 13:55:27] WARNING[31247] pbx_config.c: The use of '_.' for an extension is strongly discouraged and can have unexpecte
d behavior.  Please use '_X.' instead at line 60
[Jan 17 13:55:27] WARNING[31247] pbx_config.c: The use of '_.' for an extension is strongly discouraged and can have unexpecte
d behavior.  Please use '_X.' instead at line 61
[Jan 17 13:55:27] WARNING[31247] pbx_config.c: The use of '_.' for an extension is strongly discouraged and can have unexpecte
d behavior.  Please use '_X.' instead at line 1130
[Jan 17 13:55:27] WARNING[31247] pbx_config.c: The use of '_.' for an extension is strongly discouraged and can have unexpecte
d behavior.  Please use '_X.' instead at line 1131
[Jan 17 13:55:27] WARNING[31247] pbx_config.c: The use of '_.' for an extension is strongly discouraged and can have unexpecte
d behavior.  Please use '_X.' instead at line 1132
[Jan 17 13:55:27] WARNING[31247] pbx_config.c: Unable to include context 'from-internal' in context 'trusted'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'from-did-direct' tries to include nonexistent context 'ext-findmefollow'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'from-pstn' tries to include nonexistent context 'from-pstn-custom'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'from-internal-additional' tries to include nonexistent context 'from-internal
-additional-custom'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'bad-number' tries to include nonexistent context 'bad-number-custom'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'app-blackhole' tries to include nonexistent context 'app-blackhole-custom'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'outrt-001-9_outside' tries to include nonexistent context 'outrt-001-9_outsid
e-custom'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'outbound-allroutes' tries to include nonexistent context 'outbound-allroutes-
custom'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'ext-did-catchall' tries to include nonexistent context 'ext-did-catchall-cust
om'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'ext-did' tries to include nonexistent context 'ext-did-custom'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'ext-test' tries to include nonexistent context 'ext-test-custom'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'app-chanspy' tries to include nonexistent context 'app-chanspy-custom'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'app-zapbarge' tries to include nonexistent context 'app-zapbarge-custom'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'app-pickup' tries to include nonexistent context 'app-pickup-custom'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'app-userlogonoff' tries to include nonexistent context 'app-userlogonoff-cust
om'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'app-cf-unavailable-on' tries to include nonexistent context 'app-cf-unavailab
le-on-custom'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'app-cf-unavailable-off' tries to include nonexistent context 'app-cf-unavaila
ble-off-custom'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'app-cf-on' tries to include nonexistent context 'app-cf-on-custom'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'app-cf-off-any' tries to include nonexistent context 'app-cf-off-any-custom'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'app-cf-off' tries to include nonexistent context 'app-cf-off-custom'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'app-cf-busy-on' tries to include nonexistent context 'app-cf-busy-on-custom'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'app-cf-busy-off-any' tries to include nonexistent context 'app-cf-busy-off-an
y-custom'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'app-cf-busy-off' tries to include nonexistent context 'app-cf-busy-off-custom
'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'gabcast' tries to include nonexistent context 'gabcast-custom'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'app-gabcast' tries to include nonexistent context 'app-gabcast-custom'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'app-dictate-send' tries to include nonexistent context 'app-dictate-send-cust
om'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'app-dictate-record' tries to include nonexistent context 'app-dictate-record-
custom'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'app-recordings' tries to include nonexistent context 'app-recordings-custom'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'cidlookup' tries to include nonexistent context 'cidlookup-custom'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'app-vmmain' tries to include nonexistent context 'app-vmmain-custom'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'app-dialvm' tries to include nonexistent context 'app-dialvm-custom'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'app-pbdirectory' tries to include nonexistent context 'app-pbdirectory-custom
'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'app-callwaiting-cwon' tries to include nonexistent context 'app-callwaiting-c
won-custom'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'app-callwaiting-cwoff' tries to include nonexistent context 'app-callwaiting-
cwoff-custom'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'app-blacklist-remove' tries to include nonexistent context 'app-blacklist-rem
ove-custom'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'app-blacklist-last' tries to include nonexistent context 'app-blacklist-last-
custom'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'app-blacklist-add' tries to include nonexistent context 'app-blacklist-add-cu
stom'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'app-blacklist' tries to include nonexistent context 'app-blacklist-custom'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'app-blacklist-check' tries to include nonexistent context 'app-blacklist-chec
k-custom'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'app-zoip' tries to include nonexistent context 'app-zoip-custom'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'app-dnd-on' tries to include nonexistent context 'app-dnd-on-custom'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'app-dnd-off' tries to include nonexistent context 'app-dnd-off-custom'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'app-speakingclock' tries to include nonexistent context 'app-speakingclock-cu
stom'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'app-speakextennum' tries to include nonexistent context 'app-speakextennum-cu
stom'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'app-echo-test' tries to include nonexistent context 'app-echo-test-custom'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'app-directory' tries to include nonexistent context 'app-directory-custom'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'app-calltrace-perform' tries to include nonexistent context 'app-calltrace-pe
rform-custom'
[Jan 17 13:55:27] WARNING[31247] pbx.c: Context 'app-calltrace' tries to include nonexistent context 'app-calltrace-custom'
[Jan 17 13:55:27] WARNING[31247] cdr_odbc.c: cdr_odbc: Unable to load config for ODBC CDR's: cdr_odbc.conf
[Jan 17 13:55:27] NOTICE[31247] chan_agent.c: No agent configuration found -- agent support disabled
[Jan 17 13:55:27] NOTICE[31247] chan_mgcp.c: Unable to load config mgcp.conf, MGCP disabled
[Jan 17 13:55:27] WARNING[31247] cdr_custom.c: Failed to load configuration file. Module not activated.
[Jan 17 13:55:27] ERROR[31247] chan_gtalk.c: Unable to read config file gtalk.conf. Not loading module.
[Jan 17 13:55:27] WARNING[31247] cdr_pgsql.c: Unable to load config for PostgreSQL CDR's: cdr_pgsql.conf
[Jan 17 13:55:27] NOTICE[31247] func_odbc.c: Unable to load config for func_odbc: func_odbc.conf
[Jan 17 13:55:27] WARNING[31247] cdr_csv.c: unable to load config: cdr.conf
[Jan 17 13:55:27] ERROR[31247] pbx_dundi.c: Unable to load config dundi.conf
[Jan 17 13:55:27] ERROR[31247] res_config_mysql.c: MySQL RealTime: Failed to connect database server  on  (err 2002). Check de
bug for more info.
[Jan 17 13:55:27] WARNING[31247] res_config_mysql.c: MySQL RealTime: Couldn't establish connection. Check debug.
[Jan 17 13:55:27] NOTICE[31247] config.c: Registered Config Engine mysql
[Jan 17 13:55:27] ERROR[31247] chan_zap.c: Unable to load config zapata.conf
[Jan 17 13:55:27] ERROR[31247] app_amd.c: Configuration file amd.conf missing.
[Jan 17 13:55:27] VERBOSE[31247] logger.c:   == No hardware transcoders found.
[Jan 17 13:55:27] VERBOSE[31247] logger.c:   == Platform byte order   : LITTLE ENDIAN
[Jan 17 13:55:27] VERBOSE[31247] logger.c:     -- GLOBAL: Preferred capability (alaw|ulaw)
[Jan 17 13:55:27] WARNING[31247] chan_sccp.c: Unknown param at line 50: park = off
[Jan 17 13:55:27] VERBOSE[31247] logger.c:     -- Added empty speeddial
[Jan 17 13:55:27] WARNING[31247] chan_sccp.c: Wrong device param: device => SEP
[Jan 17 13:55:27] WARNING[31247] chan_sccp.c: Unknown param at line 62: park = off
[Jan 17 13:55:27] VERBOSE[31247] logger.c:     -- Added empty speeddial
[Jan 17 13:55:27] WARNING[31247] chan_sccp.c: Wrong device param: device => SEP

Any idea what i must do???
Guess it has something to do with the update?  

339

Installation issues / Re: Syslog flooded by 'failed to mount'

« on: January 16, 2012, 01:25:40 pm »

Thanks, i've removed the disk from the core, and my logs are more readable...

340

Installation issues / [SOLVED] Syslog flooded by 'failed to mount'

« on: January 15, 2012, 08:11:54 am »

Hey,

My syslog is flooded by a lot of problems to mount some disks. This is triggered each minute. So a bit to much information...

Code: [Select]

corius 2012-01-15 07:57:56 ookup(program): lookup for 90 failed Daemon Err
corius 2012-01-15 07:57:56 failed to mount /mnt/device/90 Daemon Err
corius 2012-01-15 07:57:56 lookup(program): lookup for 91 failed Daemon Err
corius 2012-01-15 07:57:56 failed to mount /mnt/device/91 Daemon Err
corius 2012-01-15 07:57:56 lookup(program): lookup for 89 failed Daemon Err
corius 2012-01-15 07:57:56 failed to mount /mnt/device/89
For the moment, i've got only 1 disk in the machine (sda). I was trying to add a second one, but something went/goes wrong there...
Some details from 'sudo fdisk -l':

Code: [Select]

Schijf /dev/sda: 500.1 GB, 500107862016 bytes
255 koppen, 63 sectoren/spoor, 60801 cilinders
Eenheid = cilinders van 16065 * 512 = 8225280 bytes
Schijf-ID: 0x000d6c93

 Apparaat Opstart   Begin       Einde     Blokken   ID  Systeem
/dev/sda1   *           1       59667   479275146   83  Linux
/dev/sda2           59668       60801     9108855    5  Uitgebreid
/dev/sda5           59668       60801     9108823+  82  Linux wisselgeheugen


These are following disks that give problems:

Code: [Select]

Device #89: ST31000340AS (sdb1) on corius
Device #90: ST31000340AS (sdb2) on corius
Device #91: ST31000340AS (sdb1) on corius

Can i safely remove these disks from the 'My Devices / Core' with the option delete this device?
Or must i follow a specific procedure to do this?

341

Users / Re: Is sysklogd needed?

« on: January 14, 2012, 08:01:51 am »

Are you using the MySQL backend for rsyslog, or is cacti just parsing the logs?

Nope, i'm using the mysql backend.

If you want to get fancy, you can enable remote syslog sending on your MD's, listening on the core, and then you can run a central syslog server on the core.

Other devices in my network (like the switch, routers, power sensors...) are already sending their logs to the linuxMCE machine. This is/was the whole meaning of using linuxmce.That it won't only control my infrastructure, but also monitor it. And warn me about problems. fe i receive almost daily a mail from cacti that my power consumption hits 4KW. So then i know that my girlfriend is preparing some food for me...

You might want to put up a wiki page ... so that others can follow in your footsteps...

You're right, but you know, written documentation is so hard. Trying to recall each step you made...
But i promise, next week, i'll install a new linuxmce server, and redo the whole installation of cacti with all plugins/steps...

342

Feature requests & roadmap / Re: Monitoring

« on: January 13, 2012, 02:15:52 pm »

Small example of the syslog module: http://forum.linuxmce.org/index.php/topic,12292.0.html
A pitty i can't give you limit access to it like for the graphs.

343

Users / Re: Is sysklogd needed?

« on: January 13, 2012, 02:14:29 pm »

An example of how my syslogs are looking.

Easier to look, quicker interaction/search...
At least i see that i've got a problem with my second disk for the moment...

344

Feature requests & roadmap / Re: raspberry pi

« on: January 11, 2012, 01:26:26 pm »

Just noticed that they started the production...
http://www.raspberrypi.org/

Would be nice as an orbiter no? I'm thinking to connect linuxmce with my home theater... Today i'm just using a PS3 to play some movies...

345

Users / Re: Is sysklogd needed?

« on: January 10, 2012, 08:08:57 am »

Great...

I've just installed rsyslog, and with the cacti module, i know have a nice GUI to see my logs...
Still some finetuning to do, but already i see some errors of my server that i should investigate.