Messages

346

Feature requests & roadmap / Re: Monitoring

« on: January 09, 2012, 05:12:51 pm »

Very cool, do you have a wiki how to implement this?

Not directly. But once i see what the rest thinks about it, I'll write one. I first want to see what we need/want. And then I want to see if it's possible to create a kind of template of it all. This way, people don't have to 'understand' this module, they just can use/view it...
Add it, log it, check it... And be alerted if something is wrong.


ps but in the meantime, it's really easy to install/use cacti. Just try a 'sudo apt-get install cacti' and you should be on your way.

347

Users / Is sysklogd needed?

« on: January 09, 2012, 03:27:46 pm »

Hey,

I noticed that today, sysklogd is used for the syslogging.
Is this a requirement? Or can I change this with fe rsyslog or syslog-ng?

Reason for me asking this that i would like to add a more 'GUI' based syslogging.
And also use the server for other purposes like collecting the syslogs of other machines in my network...

348

Feature requests & roadmap / Re: Monitoring

« on: January 09, 2012, 02:52:59 pm »

I finally had the time to create/install/configure a bit my monitoring.You can check it out on realtime: http://cacti.oniria.be. Login with linuxmce / lnxmc. For the moment, this is a limited user. Check out on the left the server part. Corius is the name of the server...
I'll see if I keep it like this or not (abuse, spam, hack...). I hope I can keep it open like this. At least for a while.
If you want more privilege to see it working, send me a pm...

For the moment, I just monitor some basic stuff of the server (bandwidth, disk space, load, database performance...).
I mainly use the cacti for network monitoring, power usage  of my home... And some alerting (tresholds) for some stuff (like to much power usage and so).

The plan is to add:

• templates for the services (graphs)
• templates for the asterik (graphs)
  once i started to configure my phones in there
• up/down status for services (manage)
  dns/proxy/dhcp/samba/web...
• logging module (syslog)
• Create a weathermap
  Graphical scheme with status
• ...

Let me know if you think of interesting things...
You never know what the result can be...



ps of course this is running on the same machine as linuxmce...  

349

Users / Re: Input switches

« on: January 01, 2012, 02:40:59 pm »

I've just created a GA in ETS, and added the button in it. Nothing more.
A bit similar like i did for my standalone groups (=the groups who work without the server involvement).

For the eibd.log, this is generate once i push the button.
So its data coming from the button towards the server...

When i add now a light into this 'ETS' group, it lights up once i push the button.
So the configuration is working without a server involvement.


I was thinking that there isn't data coming in from the EIB bus. But since i can read the status of the lights, i suppose this is fine?
When a light is flipped on, DCErouter.log starts generating some log files as well.


ps what do you mean with the GA definition? Are their special settings for the groups to take care off?

350

Users / Re: Input switches

« on: January 01, 2012, 02:20:57 pm »

Nope, nothing. 

I only see some movement when i push a button that is configured with a light.
But then it's the return of the relays that i see in the logs. Not the actually button push.

351

Users / Re: Input switches

« on: January 01, 2012, 08:26:45 am »

grrr, seems that the sensors don't want to play with me...
Do you need to do something special in ETS except putting the sensor in a Group Address and make it Sending?

I'm testing now with another sensor since this one is closer to my computer.
So this is the new output log for the eibd driver:

Code: [Select]

Layer 0(09004B78,4F00077D) Recv(021): 06 10 04 20 00 15 04 44 14 00 29 00 BC E0 11 33 08 07 01 00 81
Layer 1(09004B78,4F00077D) Recv(015): 04 44 14 00 29 00 BC E0 11 33 08 07 01 00 81
Layer 1(09004B78,4F00077D) Send(004): 04 44 14 00
Layer 0(09004B78,4F00077D) Send(010): 06 10 04 21 00 0A 04 44 14 00
Layer 1(09004680,4F00077D) Recv L_Data low from 1.1.51 to 1/0/7 hops: 06 T_DATA_XXX_REQ A_GroupValue_Write (small) 01
Layer 2(09004680,4F00077D) Recv L_Data low from 1.1.51 to 1/0/7 hops: 06 T_DATA_XXX_REQ A_GroupValue_Write (small) 01
Layer 3(09025290,4F00077D) Recv L_Data low from 1.1.51 to 1/0/7 hops: 06 T_DATA_XXX_REQ A_GroupValue_Write (small) 01
Layer 8(09055CD0,4F00077D) Send_Route L_Data low from 1.1.51 to 1/0/7 hops: 05 T_DATA_XXX_REQ A_GroupValue_Write (small) 01
Layer 1(09055D40,4F00077D) Send(011): 29 00 BC D0 11 33 08 07 01 00 81
Layer 0(09055D40,4F00077D) Send(017): 06 10 05 30 00 11 29 00 BC D0 11 33 08 07 01 00 81
Layer 4(090770A8,4F00077D) Recv GroupSocket(002): 00 81
Layer 7(09088524,4F00077D) Recv(002): 00 81
Layer 8(09077060,4F00077D) SendMessage(008): 00 27 11 33 08 07 00 81
ps each time i changed something, i'm doing a reload of the core. Don't think that's necessary, but it can't hurt either... (i think)

352

Users / Re: Input switches and 'sleeping scenario'

« on: December 31, 2011, 02:44:15 pm »

I've tried the doorbell function, but the result is the same. But you're right, easier to test phase 1...

I don't see anything happen in the logs. Only the 'retour' from the lights as it seems.
It's like the server isn't picking up the signal from the sensor (it's there, that i can see with the eibd dump).
But i suppose that DCErouter.log isn't triggered when the sensor isn't configured properly?

What do you've got in your sensor settings? I've got following:
PK_FloorplanObjectType    Door
Port/Channel Number    0/0/31
InputOrOutput    2
Default State    0
Alert
EK_AlertType    1

353

Installation issues / Re: Outside Access; No access with high ports?

« on: December 29, 2011, 09:40:44 pm »

You won't believe it. This was 'the law of Murphy'.

I just did some extra digging in my providers manuals (well hidden of course), and these are the ports that are blocked:

• all ports from 0 till 1023
• port 1080
• sensitive ports for abuse: 12345, 12346, 31337 tot en met 31339, 31784, 27374, 1243, 31785 > 31792, 4444, 1847, 1900, 3127

btw you're right about the stupid policy. A lot of customers are complaining about the ISP policies. But in fact, we can only choose between 2 big ISP in Belgium. And some small players, but you can guess about the pricing/quality. I dare you to find a good SIP provider over here. Welcome to Belgium...


But this is just another prove that linuxmce is doing what he must do. Just a pitty that they're so many details that can give you headache...

354

Users / Re: Input switches and 'sleeping scenario'

« on: December 29, 2011, 09:06:07 pm »

I don't see the input of the sensor. But the change of status for the lights are coming into the DCErouter.log. This log is from a GA in ETS where i've got 1 sensor and 1 switch. When i push the sensor for 0/0/31, nothing shows up in the logs.

Code: [Select]

07      12/29/11 21:00:38.159           Event #81 has no handlers <0x7cdcab90>
07      12/29/11 21:00:38.159           Received Message from 45 (V Inkom / Inkom) to -1001 (unknown / ), type 2 id 81 Event:State Changed, retry none, parameters: <0x7cdcab90>
07      12/29/11 21:00:38.159             Parameter 66(State): 1 <0x7cdcab90>
07      12/29/11 21:00:40.255           Event #81 has no handlers <0x7cdcab90>
07      12/29/11 21:00:40.255           Received Message from 45 (V Inkom / Inkom) to -1001 (unknown / ), type 2 id 81 Event:State Changed, retry none, parameters: <0x7cdcab90>
07      12/29/11 21:00:40.255             Parameter 66(State): 0 <0x7cdcab90

When I now run the eibd daemon with a local log, i see the sensor action. So we can conclude that the sensor arrives in the server?

Code: [Select]

Layer 0(087D0B78,4EFCCBB5) Recv(021): 06 10 04 20 00 15 04 4D 13 00 29 00 BC E0 11 0B 00 1F 01 00 80
Layer 1(087D0B78,4EFCCBB5) Recv(015): 04 4D 13 00 29 00 BC E0 11 0B 00 1F 01 00 80
Layer 1(087D0B78,4EFCCBB5) Send(004): 04 4D 13 00
Layer 0(087D0B78,4EFCCBB5) Send(010): 06 10 04 21 00 0A 04 4D 13 00
Layer 1(087D0680,4EFCCBB5) Recv L_Data low from 1.1.11 to 0/0/31 hops: 06 T_DATA_XXX_REQ A_GroupValue_Write (small) 00
Layer 2(087D0680,4EFCCBB5) Recv L_Data low from 1.1.11 to 0/0/31 hops: 06 T_DATA_XXX_REQ A_GroupValue_Write (small) 00
Layer 3(087F1290,4EFCCBB5) Recv L_Data low from 1.1.11 to 0/0/31 hops: 06 T_DATA_XXX_REQ A_GroupValue_Write (small) 00
Layer 8(08821CD0,4EFCCBB5) Send_Route L_Data low from 1.1.11 to 0/0/31 hops: 05 T_DATA_XXX_REQ A_GroupValue_Write (small) 00
Layer 1(08821D40,4EFCCBB5) Send(011): 29 00 BC D0 11 0B 00 1F 01 00 80
Layer 0(08821D40,4EFCCBB5) Send(017): 06 10 05 30 00 11 29 00 BC D0 11 0B 00 1F 01 00 80
Layer 4(088430A8,4EFCCBB5) Recv GroupSocket(002): 00 80
Layer 7(08854524,4EFCCBB5) Recv(002): 00 80
Layer 8(08843060,4EFCCBB5) SendMessage(008): 00 27 11 0B 00 1F 00 80

355

Users / Re: Input switches and 'sleeping scenario'

« on: December 29, 2011, 05:57:44 pm »

Finally found the time to play with this feature. But no luck...
What i've done:

In ETS

• Assign a GA to my lightswitch 0/0/31

In linuxMCE (security sensor)

• Description "S Test"
• Device Template #: 1813
• Controlled By: EIB
• Port/Channel Number = 0/0/31
• InputOrOutput= 2
• Default state = 0
• EKAlertype = 1

In linuxMCE

• event: a sensor (motion, door...) is tripped
• What device = 'S Test'
• What time = ''
• Trigger = tripped = '1'
• Light A = on (a test command here works)

But seems not to work. The lights and so are working correctly for the eib stuff.
Any idea what i'm doing wrong?


ps the idea is later on to active or shutdown the light with a pushbutton.
I don't see how i must to this (because i've got the feeling i only can or activate or deactive something).
But before we run, lets take babysteps and start with 1 action...

356

Installation issues / Re: Outside Access; No access with high ports?

« on: December 29, 2011, 01:56:25 pm »

Yep, that's the place where i did all my configuration...

In short, for me port '12345' isn't working.
'2222' is working.

357

Installation issues / Outside Access; No access with high ports?

« on: December 29, 2011, 10:40:56 am »

I've played around to get the remote access working.  My ISP blocks all ports below 1024. So i needed to use a port higher then that.
I thought of using an easy port, namely 12345. But this didn't work.  
I check with my ISP (Belgium cableprovider telenet), but of course they couldn't help me. You know those ISP, they're GOD.  
After a lot of testing and changing, i found out that when i use fe port 2222, it works. But with 12345 it doesn't?!

So if others have problems, try this (or another) port?



Any idea how this come?
If it's a restriction in the server, maybe best to let us choose between some? A drop-down menu or so? Would be a bit more userfriendly, no?

For example

Allow outside access to the website on port	80
	443
	1027
	1232
	2375
	custom

358

Users / Re: All user data on disk B

« on: December 27, 2011, 01:06:26 pm »

But isn't this very limited to my configuration?
I suggest that we put something in the field that all users can easily adapt for their needs (sources, destinations, timeframes...).

I've just noticed that several 'GUI's' exist for rdiff.
More info: http://wiki.rdiff-backup.org/wiki/index.php/GraphicalUserInterfaces#Web-based

I don't know if we can implement something like this?
Or is this a lot of manipulation on the current webmin? I don't have a clue about this. I'm happy to put some time into it. If I now how/when/where...

359

Users / Re: All user data on disk B

« on: December 27, 2011, 01:00:48 pm »

Well basiclly, this is it (an old manual i wrote for myself):

Installation of rdiff-backup

Code: [Select]

sudo apt-get install rdiff-backup
Create a backup folder (can be also remote NAS drive, external disk...). You need to do this only once. Replace everything after 'backups/' with the stuff you want (your home folder, your data folders, your...).

Code: [Select]

sudo mkdir /backups
sudo mkdir /backups/home/me
sudo mkdir /backups/home/he
sudo mkdir /backups/home/she
sudo mkdir /backups/web

Put following into a script (fe /scripts/backupData.sh)

Code: [Select]

sudo rdiff-backup /home/me /backups/home/me
sudo rdiff-backup /home/he /backups/home/he
sudo rdiff-backup /home/she /backups/home/she
sudo rdiff-backup /var/www/html /backups/web

Run now the script, you can it also put in your cron...

360

Users / Re: All user data on disk B

« on: December 27, 2011, 09:18:23 am »

feel free to architecture one, and implement it. After doing it, create a trac ticket and attach a feature patch.

Love to do it. If i knew how. 

Any guidelines/howto's around that i can use for this?
I personally don't have any clue how i could do this. I suppose it's not enough with just installing rdiff and write a short manual... :$