Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - brononius

Pages: 1 2 [3] 4 5 ... 25
31
Installation issues / Re: /"index.php isn't found
« on: December 17, 2012, 07:14:45 am »

Found it...  :-[

For another application, i needed a web pdf creator. And for this, i need to enable magic-quotes.
So in /etc/php5/apache2/php.ini, i had enabled magic-quotes-runtime.

Not sure why the admin-page of linuxmce can't live with it, but this causes the problem.
I'll see if i can find a reason for this behavoir, but for now, this problem can be 'closed'...


Sorry to bother you.....

32
Installation issues / Re: /"index.php isn't found
« on: December 16, 2012, 09:02:47 pm »
Sorry, wasn`t aware that the network range is important.
The server was running several weeks/months correctly with this config.
I`ll see if i can find out more tomorrow. Maybe i can add some debugging on apache level...

33
Installation issues / Re: /"index.php isn't found
« on: December 16, 2012, 07:15:06 pm »
Correct.

All other things are working great, like home automation, ipt, file sharing.
And apt-get is up to date...

34
Installation issues / Re: /"index.php isn't found
« on: December 16, 2012, 06:58:31 pm »
I am trying it from the inside. Tomorrow i can check it from the inside.
Strange thing is that all other sites (joomla, html) are working fine...

35
Installation issues / [SOLVED] /"index.php isn't found
« on: December 16, 2012, 12:06:57 pm »
Not sure what happend, but i can't reach my admin page anymore.
This is the error i'm recieving when i'm going to http://192.168.111.1/lmce-admin/index.php:
Quote
The requested URL /"index.php was not found on this server.

When i check my apache2 logs:
tail -f /var/log/apache2/error.log
Quote
[Sun Dec 16 12:04:23 2012] [error] [client 192.168.111.41] script '/var/www/"index.php' not found or unable to stat, referer: http://192.168.111.1/lmce-admin/
[Sun Dec 16 12:04:23 2012] [error] [client 192.168.111.41] script '/var/www/"index.php' not found or unable to stat, referer: http://192.168.111.1/lmce-admin

'm guessing it has something to do with the double quote in front of index.php, but i couldn't find this in index.php...

Other sites on the server are running fine...

36
Users / Re: Can i clean out /home/coredump?
« on: December 16, 2012, 08:01:06 am »
Problem with the log files is, to much info... ;)
I went through some of them, but couldn't find any reason why the server dies. He just dies. The lines before are each time different things. Inputs of my eib installation, file operation scripts... For the moment, he runs now 2 days without any crash. I did remove a lot of stuff that was wrong in my eyes (the IP-cam things, motion wrapper, a disk that wasn't connected anymore, a diskless mediadirector that wasn't working like it should...). So i hope it has something to do with this.


How can i read the dump? Is this a kind of zip file?

37
Users / Re: Can i clean out /home/coredump?
« on: December 14, 2012, 10:53:34 am »
Seems it has nothing to do with the IP-camera's. They're removed since yesterday (+/-10h), and the dumps started again today.
The server dies again almost each minute... And a new corefile of 500MB (?) is created each minute...

What's the best way to investigate this?


In my /var/log/pluto folder, i've got following files:

ls -lh d*
Quote
-rw-r--r-- 1 root root 1.6K 2012-12-14 10:50 deaths
-rw-r--r-- 1 root root  29K 2012-12-14 10:40 device.2012-12-14-10:40:21
-rw-r--r-- 1 root root  29K 2012-12-14 10:41 device.2012-12-14-10:41:32
-rw-r--r-- 1 root root  29K 2012-12-14 10:42 device.2012-12-14-10:42:36
-rw-r--r-- 1 root root  29K 2012-12-14 10:43 device.2012-12-14-10:43:40
-rw-r--r-- 1 root root  29K 2012-12-14 10:45 device.2012-12-14-10:45:07
-rw-r--r-- 1 root root  29K 2012-12-14 10:46 device.2012-12-14-10:46:40
-rw-r--r-- 1 root root  29K 2012-12-14 10:47 device.2012-12-14-10:47:40
-rw-r--r-- 1 root root  29K 2012-12-14 10:49 device.2012-12-14-10:49:03
-rw-r--r-- 1 root root  252 2012-12-14 09:56 dhcp_pnp.log
-rw-r--r-- 1 root root  272 2012-12-14 10:49 died_153_153
-rw-r--r-- 1 root root  272 2012-12-14 10:49 died_162_162
-rw-r--r-- 1 root root  272 2012-12-14 10:49 died_164_164
-rw-r--r-- 1 root root  272 2012-12-14 10:49 died_166_166
-rw-r--r-- 1 root root  238 2012-12-14 10:50 died__DCERouter

ls -lh Spaw*
Quote
--ws--s--t 1 root root  0 2012-12-14 10:46 SpawnDaemon_SendVoiceMailEvent.sh_10261.log
--ws--s--t 1 root root  0 2012-12-14 10:46 SpawnDaemon_SendVoiceMailEvent.sh_10263.log
--ws--s--t 1 root root  0 2012-12-14 10:47 SpawnDaemon_SendVoiceMailEvent.sh_13631.log
--ws--s--t 1 root root  0 2012-12-14 10:47 SpawnDaemon_SendVoiceMailEvent.sh_13633.log
--ws--s--t 1 root root  0 2012-12-14 10:43 SpawnDaemon_SendVoiceMailEvent.sh_1600.log
--ws--s--t 1 root root  0 2012-12-14 10:43 SpawnDaemon_SendVoiceMailEvent.sh_1618.log
--ws--s--t 1 root root  0 2012-12-14 10:49 SpawnDaemon_SendVoiceMailEvent.sh_17524.log
--ws--s--t 1 root root  0 2012-12-14 10:49 SpawnDaemon_SendVoiceMailEvent.sh_17526.log
--ws--s--t 1 root root  0 2012-12-14 10:41 SpawnDaemon_SendVoiceMailEvent.sh_26938.log
--ws--s--t 1 root root  0 2012-12-14 10:41 SpawnDaemon_SendVoiceMailEvent.sh_26940.log
--ws--s--t 1 root root  0 2012-12-14 10:42 SpawnDaemon_SendVoiceMailEvent.sh_30511.log
--ws--s--t 1 root root  0 2012-12-14 10:42 SpawnDaemon_SendVoiceMailEvent.sh_30513.log
--ws--s--t 1 root root  0 2012-12-14 10:45 SpawnDaemon_SendVoiceMailEvent.sh_6485.log
--ws--s--t 1 root root  0 2012-12-14 10:45 SpawnDaemon_SendVoiceMailEvent.sh_6487.log
--ws--s--t 1 root root  0 2012-12-14 10:46 Spawn_start-asterisk_10510.log
--ws--s--t 1 root root  0 2012-12-14 10:47 Spawn_start-asterisk_13803.log
--ws--s--t 1 root root  0 2012-12-14 10:49 Spawn_start-asterisk_17747.log
--ws--s--t 1 root root  0 2012-12-14 10:43 Spawn_start-asterisk_1790.log
--ws--s--t 1 root root  0 2012-12-14 10:41 Spawn_start-asterisk_27143.log
--ws--s--t 1 root root  0 2012-12-14 10:42 Spawn_start-asterisk_30623.log
--ws--s--t 1 root root  0 2012-12-14 10:45 Spawn_start-asterisk_6692.log
--ws--s--t 1 root root 22 2012-12-14 10:47 Spawn_storagedevices_10650.log
--ws--s--t 1 root root 22 2012-12-14 10:47 Spawn_storagedevices_10740.log
--ws--s--t 1 root root 22 2012-12-14 10:47 Spawn_storagedevices_10750.log
--ws--s--t 1 root root 22 2012-12-14 10:47 Spawn_storagedevices_10758.log
--ws--s--t 1 root root 22 2012-12-14 10:47 Spawn_storagedevices_10772.log
--ws--s--t 1 root root 22 2012-12-14 10:47 Spawn_storagedevices_10786.log
--ws--s--t 1 root root 22 2012-12-14 10:47 Spawn_storagedevices_10794.log
--ws--s--t 1 root root 22 2012-12-14 10:48 Spawn_storagedevices_14137.log
--ws--s--t 1 root root 22 2012-12-14 10:48 Spawn_storagedevices_14165.log
--ws--s--t 1 root root 22 2012-12-14 10:48 Spawn_storagedevices_14169.log
....


more deaths
Code: [Select]
Fri Dec 14 10:40:14 CET 2012 DCERouter died
Fri Dec 14 10:41:07 CET 2012 153 died
Fri Dec 14 10:41:07 CET 2012 164 died
Fri Dec 14 10:41:07 CET 2012 162 died
Fri Dec 14 10:41:08 CET 2012 166 died
Fri Dec 14 10:41:26 CET 2012 DCERouter died
Fri Dec 14 10:42:11 CET 2012 153 died
Fri Dec 14 10:42:12 CET 2012 164 died
Fri Dec 14 10:42:12 CET 2012 166 died
Fri Dec 14 10:42:12 CET 2012 162 died
...


And following corefiles:

ls -lh /home/coredump/1/
Quote
total 42M
-rw------- 1 root root 550M 2012-12-14 10:40 core_DCERouter_1355478014_11
-rw------- 1 root root 550M 2012-12-14 10:41 core_DCERouter_1355478085_6
-rw------- 1 root root 550M 2012-12-14 10:42 core_DCERouter_1355478149_11
-rw------- 1 root root 560M 2012-12-14 10:43 core_DCERouter_1355478214_11

38
Installation issues / Re: [SOLVED] IP Camera in 1004
« on: December 13, 2012, 03:52:23 pm »

I removed all IP-camera's (4 pieces) since the core keeps dying.
And for more then 24 hours, no problems.

When i added the motion wrapper and IP-camera's again, the core immediate starts dying each +/- 2 minutes...

Let me know if can help in any way!


39
Users / Re: Can i clean out /home/coredump?
« on: December 13, 2012, 03:48:31 pm »
Me too.   :P

I think it's related to the IP-camera issue.

But since i'm using a small SSD card of 60GB for my os, i'm trying to keep the diskspace as healthy as possible.
So the dumps will be dumped. Thanks!

40
Users / Can i clean out /home/coredump?
« on: December 13, 2012, 11:32:02 am »
Hey,

I've noticed that i've got about 5gig of coredumps in /home/coredump.
Most files are from days ago.

I'm wondering if i can safetly remove these files.
Or will this be done automaticly?


41
Users / Re: Pluto_media over 5,5GB?
« on: December 12, 2012, 08:05:28 am »
When i check this today, i've got following after the 'DELETE FROM File WHERE Missing = 1;'

Database pluto_media:
      table FILE
            Records: ~3,608,448
            Size: 4,1 GB
      table FILE_ATTRIBUTE
            Records: ~2,470,705
            Size: 310,7 MB


I've got some media, but 4gigs of 'inventory' in a database is a bit much, no?
And 3 million records? I don't think i got this amount of files...  :-[

Is there a way i can clean out the whole database/table and start over?
I suppose a purge of the table FILE isn't a good idea?

42
Installation issues / Re: [SOLVED] IP Camera in 1004
« on: December 10, 2012, 09:39:11 am »
I think i'm having a simular issue.
After a complete reinstallation of my machine, my camera snapshots (admin>security>view camera's) sometimes show by refresh, sometimes not.

When i open a log of an IP-camera, i've got:

Quote from: sudo tail -50 340_Advanced_IP_Camera.log
var oray_type=0;
var upnp_status=0;
 <0xb7769b70>
05   12/10/12 9:33:21.978      InputStatusChanged: old status = 0, new status = 0 <0xb7769b70>
Return code: 134
3   12/10/12 09:33:22   340 (spawning-device)   Device died... count=49/50 dev=340
Mon Dec 10 09:33:22 CET 2012 died
========== NEW LOG SECTION ==========
1   12/10/12 09:33:32   340 (spawning-device)   Starting... 50
1   12/10/12 09:33:32   340 (spawning-device)   Found /usr/pluto/bin/Advanced_IP_Camera
05   12/10/12 9:33:32.757      m_vectEventMethod.size() = 5. Configured EventMethods: <0xb76f66f0>
05   12/10/12 9:33:32.757      GetConfig(): EventMethod 1, m_bRunning = 26, m_sMethod = urlPoll, m_sURL = /get_status.cgi, m_iInterval = 10, m_vectInputDevices = [ m_dwPK_Device = 341, m_dwFK_DeviceTemplate = 54, status = (null), m_sTriggerMethod = pattern, m_sPatternOn = var alarm_status=1;, m_sPatternOff = var alarm_status=0;,  ] <0xb76f66f0>
05   12/10/12 9:33:32.757      m_mapPK_Device_OutputDevice.size() = 0. Configured OutputDevices: <0xb76f66f0>
05   12/10/12 9:33:32.758      Creating child 341 <0xb76f66f0>
05   12/10/12 9:33:32.758      Note: Device manager has attached a device of type 54 that this has no custom event handler for.  It will not fire events. <0xb76f66f0>
05   12/10/12 9:33:32.758      Note: Device manager has attached a device of type 54 that this has no custom handler for.  This is normal for IR. <0xb76f66f0>
05   12/10/12 9:33:32.765      InputStatusChanged: trigger = var alias='Sentio';
var now=236957;
var tz=-7200;
var alarm_status=0;
var ddns_status=0;
var <0xb76f5b70>
05   12/10/12 9:33:32.765      InputStatusChanged: old status = 0, new status = 0 <0xb76f5b70>
05   12/10/12 9:33:32.765      InputStatusChanged: trigger = var now=236957;
var tz=-7200;
var alarm_status=0;
var ddns_status=0;
var ddns_host='';
var oray_type=0;
var  <0xb76f5b70>
05   12/10/12 9:33:32.765      InputStatusChanged: old status = 0, new status = 0 <0xb76f5b70>
05   12/10/12 9:33:32.765      InputStatusChanged: trigger = var tz=-7200;
var alarm_status=0;
var ddns_status=0;
var ddns_host='';
var oray_type=0;
var upnp_status=0;
 <0xb76f5b70>
05   12/10/12 9:33:32.765      InputStatusChanged: old status = 0, new status = 0 <0xb76f5b70>
05   12/10/12 9:33:32.765      InputStatusChanged: trigger = var alarm_status=0;
var ddns_status=0;
var ddns_host='';
var oray_type=0;
var upnp_status=0;
 <0xb76f5b70>
05   12/10/12 9:33:32.765      InputStatusChanged: old status = 0, new status = 0 <0xb76f5b70>
Return code: 134
3   12/10/12 09:33:33   340 (spawning-device)   Device died... count=50/50 dev=340
Mon Dec 10 09:33:33 CET 2012 died
3   12/10/12 09:33:43   340 (spawning-device)   Aborting restart of device 340...

43
Users / Re: [SOLVED] Events: Stop ringing extension
« on: December 05, 2012, 11:13:01 am »
I vote, i don't care... :-[

I had a problem, linuxMCE couldn't provide me a solution 'out-of-the-box', and i found a solution.

Is it a good solution? I'm sure there are better ways. But what is good?
This is just one of the biggest advantages of Linux(mce).  That you're free to do whatever you want with it.


And i didn't added a feature request. Since i don't have a clue what/how/why/where this is.

44
Users / Re: [SOLVED] Events: Stop ringing extension
« on: December 05, 2012, 08:39:10 am »
Maybe worth a page in the wiki

For the moment, i'm gathering everything on my own intranet: linuxmce and eibd+events...  :-\ 
For me personally, the linuxmce wiki is to much chaos. I can't find an overview in it. But this is another topic...

I'm thinking to create a kind of 'event' scenario's. Situations from the real life... Where people can see what's possible with linuxmce...

45
Users / Re: Events: Stop ringing extension
« on: December 04, 2012, 03:34:48 pm »
I found a solution that works for me. ;)

First create some scripts files:

more /scripts/sys_call_doorbell_201_org.call
Code: [Select]
Channel: Local/201@from-internal
callerid: "Deurbel" <200>
WaitTime: 3
Context: outgoing
Extension: 200
Priority: 1

more /scripts/sys_call_doorbell_205_org.call
Code: [Select]
Channel: Local/205@from-internal
callerid: "Deurbel" <200>
WaitTime: 3
Context: outgoing
Extension: 200
Priority: 1

...
Create this for all you phone extension. Or at least fo the phones you want to have in this scenario.
 
Then you can create a script to call the phones. You can put nice sequences in it, all depending on your house.

more /scripts/sys_call_launch_doorbell_normal.sh
Code: [Select]
#!/bin/bash
 
cp /scripts/sys_call_doorbell_201_org.call /scripts/sys_call_doorbell_201.call
mv /scripts/sys_call_doorbell_201.call /var/spool/asterisk/outgoing/.
cp /scripts/sys_call_doorbell_204_org.call /scripts/sys_call_doorbell_204.call
mv /scripts/sys_call_doorbell_204.call /var/spool/asterisk/outgoing/.
cp /scripts/sys_call_doorbell_205_org.call /scripts/sys_call_doorbell_205.call
mv /scripts/sys_call_doorbell_205.call /var/spool/asterisk/outgoing/.
cp /scripts/sys_call_doorbell_206_org.call /scripts/sys_call_doorbell_206.call
mv /scripts/sys_call_doorbell_206.call /var/spool/asterisk/outgoing/.
sleep 1
cp /scripts/sys_call_doorbell_202_org.call /scripts/sys_call_doorbell_202.call
mv /scripts/sys_call_doorbell_202.call /var/spool/asterisk/outgoing/.
cp /scripts/sys_call_doorbell_203_org.call /scripts/sys_call_doorbell_203.call
mv /scripts/sys_call_doorbell_203.call /var/spool/asterisk/outgoing/.
cp /scripts/sys_call_doorbell_207_org.call /scripts/sys_call_doorbell_207.call
mv /scripts/sys_call_doorbell_207.call /var/spool/asterisk/outgoing/.
cp /scripts/sys_call_doorbell_208_org.call /scripts/sys_call_doorbell_208.call
mv /scripts/sys_call_doorbell_208.call /var/spool/asterisk/outgoing/.
sleep 1
cp /scripts/sys_call_doorbell_201_org.call /scripts/sys_call_doorbell_201.call
mv /scripts/sys_call_doorbell_201.call /var/spool/asterisk/outgoing/.
cp /scripts/sys_call_doorbell_204_org.call /scripts/sys_call_doorbell_204.call
mv /scripts/sys_call_doorbell_204.call /var/spool/asterisk/outgoing/.
cp /scripts/sys_call_doorbell_205_org.call /scripts/sys_call_doorbell_205.call
mv /scripts/sys_call_doorbell_205.call /var/spool/asterisk/outgoing/.
cp /scripts/sys_call_doorbell_206_org.call /scripts/sys_call_doorbell_206.call
mv /scripts/sys_call_doorbell_206.call /var/spool/asterisk/outgoing/.
And another scenario for 'night' simulation:

more /scripts/sys_call_launch_doorbell_atelier.sh
Code: [Select]
#!/bin/bash
 
cp /scripts/sys_call_doorbell_201_org.call /scripts/sys_call_doorbell_201.call
mv /scripts/sys_call_doorbell_201.call /var/spool/asterisk/outgoing/.
cp /scripts/sys_call_doorbell_204_org.call /scripts/sys_call_doorbell_204.call
mv /scripts/sys_call_doorbell_204.call /var/spool/asterisk/outgoing/.
sleep 1
cp /scripts/sys_call_doorbell_203_org.call /scripts/sys_call_doorbell_203.call
mv /scripts/sys_call_doorbell_203.call /var/spool/asterisk/outgoing/.
cp /scripts/sys_call_doorbell_208_org.call /scripts/sys_call_doorbell_208.call
mv /scripts/sys_call_doorbell_208.call /var/spool/asterisk/outgoing/.
sleep 1
cp /scripts/sys_call_doorbell_201_org.call /scripts/sys_call_doorbell_201.call
mv /scripts/sys_call_doorbell_201.call /var/spool/asterisk/outgoing/.
cp /scripts/sys_call_doorbell_204_org.call /scripts/sys_call_doorbell_204.call
mv /scripts/sys_call_doorbell_204.call /var/spool/asterisk/outgoing/.

Once this is build, you can start using them when somebody push the doorbel. It just a matter of triggering the right scenario (app server / spawn application)...
See attachments for more information on this...

ps you can even call your cellphone when somebody hits the doorbell... ;)

Pages: 1 2 [3] 4 5 ... 25