FHEM Forum

FHEM => fhem-users => Thema gestartet von: Guest am 09 November 2012, 08:03:35

Titel: perl on synology diskstation 412+ running amok
Beitrag von: Guest am 09 November 2012, 08:03:35
Originally posted by: <email address deleted>

I moved installation from 410j (ARM) to 412+ (Intel Atom). FHEM seems to
work, but the perl process is eating up close to 25% of the available
CPU-power:

top - 07:50:43 up 18:30, 2 users, load average: 1.62, 1.68, 1.79
Tasks: 153 total, 1 running, 152 sleeping, 0 stopped, 0 zombie
Cpu(s): 17.9%us, 0.7%sy, 0.0%ni, 81.3%id, 0.1%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 1013812k total, 709104k used, 304708k free, 161572k buffers
Swap: 2097084k total, 12k used, 2097072k free, 383028k cached

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
7407 root 20 0 11444 9504 1008 S 64 0.9 262:44.27 perl
7878 root 20 0 12008 3584 1764 S 0 0.4 1:05.32 snmpd
 
Any ideas? Should I have recompiled/installed from scratch? Thanks for any
reply...

--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com
Titel: Re: perl on synology diskstation 412+ running amok
Beitrag von: rudolfkoenig am 09 November 2012, 09:29:14
                                                   

> Any ideas? Should I have recompiled/installed from scratch? Thanks for any
> reply...

Start fhem with
  attr global logfile -
  attr global verbose 5
  attr global mseclog
and watch the output in the terminal. Maybe you get some ideas, where the time
is spent.

--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com
Titel: Re: perl on synology diskstation 412+ running amok
Beitrag von: Guest am 09 November 2012, 12:10:00
Originally posted by: <email address deleted>

Nothing on the terminal and then it dies... :-(

~ # perl /opt/fhem/bin/fhem.pl /opt/fhem/etc/fhem.cfg
2012.11.09 11:50:30 5: Cmd: >attr global mseclog<
2012.11.09 11:50:30.155 5: Cmd: >attr global autoload_undefined_devices 1<
2012.11.09 11:50:30.155 5: Cmd: >attr global logfile
/opt/fhem/var/log/fhem_%Y_%m.log<

~ # ps -ef | grep perl
root      7390     1  0 Nov08 ?        00:00:03 perl tcptee.pl --loop
192.168.1.11:1000:192.168.1.51:1000
root      7391     1  0 Nov08 ?        00:00:03 perl tcptee.pl --loop
192.168.1.12:1000:192.168.1.52:1000
root     12777     1  4 11:50 pts/2    00:00:00 perl /opt/fhem/bin/fhem.pl
/opt/fhem/etc/fhem.cfg

nothing else on the terminal...

logfile:

2012.11.09 11:53:42.464 5: HMLAN_Parse: hmlan1
HHM-LAN-IF,03C1,GEQ0208181,12FF04
2012.11.09 11:53:43.460 5: CUL/RAW:
/K31846168E4^M                              
2012.11.09 11:53:43.460 2: CUL1: K31846168
-88                                  
2012.11.09 11:53:43.460 5: CUL1 dispatch
K31846168                              
2012.11.09 11:53:43.462 4: CUL_WS S300TH DEV_WS_4_Bad: T: 18.3  H:
68.6        
2012.11.09 11:53:43.462 5: Triggering DEV_WS_4_Bad (3
changes)                  
2012.11.09 11:53:43.462 5: DEV_WS_4_Bad trigger: Checking FL_ALL_TEMPHUM
for not
2012.11.09 11:53:43.527 5: DEV_WS_4_Bad trigger: Checking FL_ZwSt_ALL for
notify
2012.11.09 11:53:43.527 5: DEV_WS_4_Bad trigger: Checking FileLog_BidCoS_RF
for
2012.11.09 11:53:43.527 5: DEV_WS_4_Bad trigger: Checking
FileLog_DEV_EM_1_EL fo
2012.11.09 11:53:43.527 5: DEV_WS_4_Bad trigger: Checking
FileLog_DEV_EM_9_GS fo
2012.11.09 11:53:43.527 5: DEV_WS_4_Bad trigger: Checking
FileLog_DEV_RFR_07 for
2012.11.09 11:53:43.527 5: DEV_WS_4_Bad trigger: Checking FileLog_DEV_WS_1
2012.11.09 11:53:43.527 5: DEV_WS_4_Bad trigger: Checking
FileLog_DEV_WS_2_Schla
2012.11.09 11:53:43.528 5: DEV_WS_4_Bad trigger: Checking FileLog_DEV_WS_3
2012.11.09 11:53:43.528 5: DEV_WS_4_Bad trigger: Checking
FileLog_DEV_WS_4_Bad f
2012.11.09 11:53:43.627 5: DEV_WS_4_Bad trigger: Checking
FileLog_DEV_WS_5_Wohne
2012.11.09 11:53:43.627 5: DEV_WS_4_Bad trigger: Checking
FileLog_DEV_WS_6_Gast
2012.11.09 11:53:43.627 5: DEV_WS_4_Bad trigger: Checking
FileLog_DEV_WS_7_Speic
2012.11.09 11:53:43.627 5: DEV_WS_4_Bad trigger: Checking
FileLog_DEV_WS_8_Ausse
2012.11.09 11:53:43.627 5: DEV_WS_4_Bad trigger: Checking
FileLog_Dev.Blind.Gast
2012.11.09 11:53:43.628 5: DEV_WS_4_Bad trigger: Checking
FileLog_Dev.Blind.Hall
2012.11.09 11:53:43.628 5: DEV_WS_4_Bad trigger: Checking
FileLog_Dev.Blind.K.NN
2012.11.09 11:53:43.628 5: DEV_WS_4_Bad trigger: Checking
FileLog_Dev.Blind.K.WN
2012.11.09 11:53:43.628 5: DEV_WS_4_Bad trigger: Checking
FileLog_Dev.Blind.K.WS
2012.11.09 11:53:43.628 5: DEV_WS_4_Bad trigger: Checking
FileLog_Dev.Blind.OG.S
2012.11.09 11:53:43.628 5: DEV_WS_4_Bad trigger: Checking
FileLog_Dev.Blind.OG.W
2012.11.09 11:53:43.628 5: DEV_WS_4_Bad trigger: Checking
FileLog_Dev.Blind.OZi.
2012.11.09 11:53:43.628 5: DEV_WS_4_Bad trigger: Checking
FileLog_Dev.Blind.OZi.
2012.11.09 11:53:43.629 5: DEV_WS_4_Bad trigger: Checking
FileLog_Dev.Blind.OZi.
2012.11.09 11:53:43.629 5: DEV_WS_4_Bad trigger: Checking
FileLog_Dev.Blind.WZ f
2012.11.09 11:53:43.629 5: DEV_WS_4_Bad trigger: Checking
FileLog_Dev.Hzg.Keller
2012.11.09 11:53:43.629 5: DEV_WS_4_Bad trigger: Checking
FileLog_Dev.WDisp.Kuec
2012.11.09 11:53:43.629 5: DEV_WS_4_Bad trigger: Checking
FileLog_Dev.WDisp.OZi
2012.11.09 11:53:43.629 5: DEV_WS_4_Bad trigger: Checking FileLog_FHZ for
notify
2012.11.09 11:53:43.629 5: DEV_WS_4_Bad trigger: Checking
FileLog_FS20_8273fb fo
2012.11.09 11:53:43.629 5: DEV_WS_4_Bad trigger: Checking
FileLog_KFM_100E_Displ
2012.11.09 11:53:43.630 5: DEV_WS_4_Bad trigger: Checking
FileLog_KFM_100E_Senso
2012.11.09 11:53:43.630 5: DEV_WS_4_Bad trigger: Checking FileLog_KS550 for
noti
2012.11.09 11:53:43.630 5: DEV_WS_4_Bad trigger: Checking FileLog_ZwStDim1
for n
2012.11.09 11:53:43.630 5: DEV_WS_4_Bad trigger: Checking FileLog_ZwSt_1
for not
2012.11.09 11:53:43.630 5: DEV_WS_4_Bad trigger: Checking
FileLog_ZwSt_1_CHN_1 f
2012.11.09 11:53:43.630 5: DEV_WS_4_Bad trigger: Checking FileLog_ZwSt_2
for not
2012.11.09 11:53:43.630 5: DEV_WS_4_Bad trigger: Checking FileLog_ZwSt_3
for not
2012.11.09 11:53:43.630 5: DEV_WS_4_Bad trigger: Checking FileLog_ZwSt_4
for not
2012.11.09 11:53:43.631 5: DEV_WS_4_Bad trigger: Checking WEB for
notify        
2012.11.09 11:53:43.631 5: DEV_WS_4_Bad trigger: Checking WEBS for
notify      
2012.11.09 11:53:43.631 5: DEV_WS_4_Bad trigger: Checking autocreate for
notify
2012.11.09 11:53:49.482 5: HMLAN/RAW:
/HHM-LAN-IF,03C1,GEQ0208468,12D0C4,9CE046,
                                                                               

2012.11.09 11:53:49.482 5: HMLAN_Parse: hmlan2
HHM-LAN-IF,03C1,GEQ0208468,12D0C4
2012.11.09 11:53:52.485 5: HMLAN/RAW:
/HHM-LAN-IF,03C1,GEQ0208181,12FF04,9CE046,
                                                                               

2012.11.09 11:53:52.485 5: HMLAN_Parse: hmlan1
HHM-LAN-IF,03C1,GEQ0208181,12FF04
2012.11.09 11:53:59.492 5: HMLAN/RAW:
/HHM-LAN-IF,03C1,GEQ0208468,12D0C4,9CE046,
                                                                               

2012.11.09 11:53:59.493 5: HMLAN_Parse: hmlan2
HHM-LAN-IF,03C1,GEQ0208468,12D0C4
2012.11.09 11:54:01.496 5: Triggering global (1
changes)                        
2012.11.09 11:54:01.497 5: global trigger: Checking FL_ALL_TEMPHUM for
notify  
2012.11.09 11:54:01.497 5: global trigger: Checking FL_ZwSt_ALL for
notify      
2012.11.09 11:54:01.497 5: global trigger: Checking FileLog_BidCoS_RF for
notify
2012.11.09 11:54:01.497 5: global trigger: Checking FileLog_DEV_EM_1_EL for
noti
2012.11.09 11:54:01.497 5: global trigger: Checking FileLog_DEV_EM_9_GS for
noti
2012.11.09 11:54:01.497 5: global trigger: Checking FileLog_DEV_RFR_07 for
notif
2012.11.09 11:54:01.497 5: global trigger: Checking FileLog_DEV_WS_1
2012.11.09 11:54:01.498 5: global trigger: Checking
FileLog_DEV_WS_2_Schlafen fo
2012.11.09 11:54:01.498 5: global trigger: Checking FileLog_DEV_WS_3
2012.11.09 11:54:01.498 5: global trigger: Checking FileLog_DEV_WS_4_Bad
for not
2012.11.09 11:54:01.498 5: global trigger: Checking FileLog_DEV_WS_5_Wohnen
for
2012.11.09 11:54:01.498 5: global trigger: Checking FileLog_DEV_WS_6_Gast
for no
2012.11.09 11:54:01.498 5: global trigger: Checking
FileLog_DEV_WS_7_Speicher fo
2012.11.09 11:54:01.498 5: global trigger: Checking FileLog_DEV_WS_8_Aussen
for
2012.11.09 11:54:01.498 5: global trigger: Checking FileLog_Dev.Blind.Gast
for n
2012.11.09 11:54:01.498 5: global trigger: Checking FileLog_Dev.Blind.Halle
for
2012.11.09 11:54:01.499 5: global trigger: Checking FileLog_Dev.Blind.K.NNW
for
2012.11.09 11:54:01.499 5: global trigger: Checking FileLog_Dev.Blind.K.WNW
for
2012.11.09 11:54:01.499 5: global trigger: Checking FileLog_Dev.Blind.K.WSW
for
2012.11.09 11:54:01.499 5: global trigger: Checking FileLog_Dev.Blind.OG.S
for n
2012.11.09 11:54:01.499 5: global trigger: Checking FileLog_Dev.Blind.OG.W
for n
2012.11.09 11:54:01.499 5: global trigger: Checking
FileLog_Dev.Blind.OZi.NNO fo
2012.11.09 11:54:01.499 5: global trigger: Checking
FileLog_Dev.Blind.OZi.ONO fo
2012.11.09 11:54:01.499 5: global trigger: Checking
FileLog_Dev.Blind.OZi.SO for
2012.11.09 11:54:01.500 5: global trigger: Checking FileLog_Dev.Blind.WZ
for not
2012.11.09 11:54:01.500 5: global trigger: Checking
FileLog_Dev.Hzg.Keller.Regle
2012.11.09 11:54:01.500 5: global trigger: Checking
FileLog_Dev.WDisp.Kueche for
2012.11.09 11:54:01.500 5: global trigger: Checking FileLog_Dev.WDisp.OZi
for no
2012.11.09 11:54:01.500 5: global trigger: Checking FileLog_FHZ for
notify      
2012.11.09 11:54:01.500 5: global trigger: Checking FileLog_FS20_8273fb for
noti
2012.11.09 11:54:01.500 5: global trigger: Checking
FileLog_KFM_100E_Display for
2012.11.09 11:54:01.500 5: global trigger: Checking FileLog_KFM_100E_Sensor
for
2012.11.09 11:54:01.501 5: global trigger: Checking FileLog_KS550 for
notify    
2012.11.09 11:54:01.501 5: global trigger: Checking FileLog_ZwStDim1 for
notify
2012.11.09 11:54:01.501 5: global trigger: Checking FileLog_ZwSt_1 for
notify  
2012.11.09 11:54:01.501 5: global trigger: Checking FileLog_ZwSt_1_CHN_1
for not
2012.11.09 11:54:01.501 5: global trigger: Checking FileLog_ZwSt_2 for
notify  
2012.11.09 11:54:01.501 5: global trigger: Checking FileLog_ZwSt_3 for
notify  
2012.11.09 11:54:01.501 5: global trigger: Checking FileLog_ZwSt_4 for
notify  
2012.11.09 11:54:01.501 5: global trigger: Checking WEB for
notify              
2012.11.09 11:54:01.501 5: global trigger: Checking WEBS for
notify            
2012.11.09 11:54:01.501 5: global trigger: Checking autocreate for
notify      
2012.11.09 11:54:01.502 0: Server
shutdown                                      
2012.11.09 11:54:01.502 2: SW:
X00                                              

?

--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com
Titel: Re: perl on synology diskstation 412+ running amok
Beitrag von: rudolfkoenig am 10 November 2012, 18:19:30
                                                   

...
> 2012.11.09 11:54:01.499 5: global trigger: Checking FileLog_Dev.Blind.OG.S
> for n

The log you posted is strange, as some words are missing sometimes:


...
> 2012.11.09 11:54:01.502 0: Server shutdown                                      

Since I do not see a shutdown command entered, this may be caused by a "kill
-TERM" or "kill -INT".  Possibly the system has not enough memory, and Linux is
trying to shoot down big processes?

--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com
Titel: Re: perl on synology diskstation 412+ running amok
Beitrag von: Guest am 10 November 2012, 23:19:20
Originally posted by: <email address deleted>

* Regarding sutdown/memory:

Synology 412+ has 1 GB of RAM, in my case almost all unused.  See
top-output in my first post.

Version: Server started (version 5.2+SVN from 2012-05-13.

Does that help?

* Regarding CPU-hogging:

Since restart I have not witnessed any high perl load on the CPU anymore...

Strange. I'll monitor this and let you know if something new happens.

--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com