March 2016 - paradm@ins.uni-bonn.de

[Paradm] CRON-APT completed on peak64bm-3 [/etc/cron-apt/config]
by root＠ins.uni-bonn.de 30 Mar '16

30 Mar '16

CRON-APT RUN [/etc/cron-apt/config]: Wed Mar 30 04:00:01 CEST 2016 CRON-APT SLEEP: 1329, Wed Mar 30 04:22:10 CEST 2016 CRON-APT ACTION: 5-install CRON-APT LINE: /usr/bin/aptitude -o Acquire::http::Dl-Limit=2000 dist-upgrade -y -o APT:Get:Show-Upgraded=true Reading package lists... Building dependency tree... Reading state information... Reading extended state information... Initializing package states... The following packages will be upgraded: ins-config-atacama 1 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/13.3 kB of archives. After unpacking 0 B will be used. Writing extended state information... Setting up ins-config-atacama (2015.10.08-14.21.52) ... Configuration file `/etc/apt/sources.list.atacama' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** sources.list.atacama (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing ins-config-atacama (--configure): EOF on stdin at conffile prompt No apport report written because MaxReports is reached already Errors were encountered while processing: ins-config-atacama E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up ins-config-atacama (2015.10.08-14.21.52) ... Configuration file `/etc/apt/sources.list.atacama' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** sources.list.atacama (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing ins-config-atacama (--configure): EOF on stdin at conffile prompt Errors were encountered while processing: ins-config-atacama Reading package lists... Building dependency tree... Reading state information... Reading extended state information... Initializing package states...

1 0

[Paradm] CRON-APT completed on peak64bm-4 [/etc/cron-apt/config]
by root＠ins.uni-bonn.de 30 Mar '16

30 Mar '16

CRON-APT RUN [/etc/cron-apt/config]: Wed Mar 30 04:00:01 CEST 2016 CRON-APT SLEEP: 1092, Wed Mar 30 04:18:13 CEST 2016 CRON-APT ACTION: 5-install CRON-APT LINE: /usr/bin/aptitude -o Acquire::http::Dl-Limit=2000 dist-upgrade -y -o APT:Get:Show-Upgraded=true Reading package lists... Building dependency tree... Reading state information... Reading extended state information... Initializing package states... The following packages will be upgraded: ins-config-atacama 1 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/13.3 kB of archives. After unpacking 0 B will be used. Writing extended state information... Setting up ins-config-atacama (2015.10.08-14.21.52) ... Configuration file `/etc/apt/sources.list.atacama' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** sources.list.atacama (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing ins-config-atacama (--configure): EOF on stdin at conffile prompt No apport report written because MaxReports is reached already Errors were encountered while processing: ins-config-atacama E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up ins-config-atacama (2015.10.08-14.21.52) ... Configuration file `/etc/apt/sources.list.atacama' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** sources.list.atacama (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing ins-config-atacama (--configure): EOF on stdin at conffile prompt Errors were encountered while processing: ins-config-atacama Reading package lists... Building dependency tree... Reading state information... Reading extended state information... Initializing package states...

1 0

[Paradm] CRON-APT completed on peak64bm-1 [/etc/cron-apt/config]
by root＠ins.uni-bonn.de 30 Mar '16

30 Mar '16

CRON-APT RUN [/etc/cron-apt/config]: Wed Mar 30 04:00:01 CEST 2016 CRON-APT SLEEP: 31, Wed Mar 30 04:00:32 CEST 2016 CRON-APT ACTION: 5-install CRON-APT LINE: /usr/bin/aptitude -o Acquire::http::Dl-Limit=2000 dist-upgrade -y -o APT:Get:Show-Upgraded=true Reading package lists... Building dependency tree... Reading state information... Reading extended state information... Initializing package states... The following packages will be upgraded: ins-config-atacama 1 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/13.3 kB of archives. After unpacking 0 B will be used. Writing extended state information... Setting up ins-config-atacama (2015.10.08-14.21.52) ... Configuration file `/etc/apt/sources.list.atacama' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** sources.list.atacama (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing ins-config-atacama (--configure): EOF on stdin at conffile prompt No apport report written because MaxReports is reached already Errors were encountered while processing: ins-config-atacama E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up ins-config-atacama (2015.10.08-14.21.52) ... Configuration file `/etc/apt/sources.list.atacama' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** sources.list.atacama (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing ins-config-atacama (--configure): EOF on stdin at conffile prompt Errors were encountered while processing: ins-config-atacama Reading package lists... Building dependency tree... Reading state information... Reading extended state information... Initializing package states...

1 0

[Paradm] Critical Alarm ist aufgetreten in der LiegenschaftINS Uni Bonn Himalaya am 29.03.2016 10:05:10;
by klima＠ins.uni-bonn.de 29 Mar '16

29 Mar '16

Ein Critical Alarm ist aufgetreten. Zeit: 29.03.2016 10:05:10 \Liegenschaft: INS Uni Bonn Himalaya Regler: INS_KAELTE_2 Grund: Alarm kommend Datenpunkt: K21_Störumschaltun Wert: AUS Alarmart: Critical ----------------------- gesendet von Centraline Arena Copyright © 2006..2008, Honeywell 2.1.0.170 alarm-id: 1c0f7a63-b311-495c-8fb5-1b9acf80007e destination-id: e3861b7a-be20-4b4f-8f65-853d8fe56bf8

1 0

[Paradm] Arena Alarm
by klima＠ins.uni-bonn.de 29 Mar '16

29 Mar '16

Ein Critical Alarm ist aufgetreten. Zeit: 29.03.2016 10:05:10 Anlage: #Anlage# Regler: #Regler# Alarmgrund: Alarm kommend Device Location: K21_Störumschaltun Wert: AUS Alarmart: Critical ----------------------- gesendet von Centraline Arena Copyright © 2006..2008, Honeywell 2.1.0.170 alarm-id: 1c0f7a63-b311-495c-8fb5-1b9acf80007e destination-id: 025adbc6-be4d-4df3-bb65-6360857e7bbe

1 0

[Paradm] Arena Alarm
by klima＠ins.uni-bonn.de 29 Mar '16

29 Mar '16

Ein Critical Alarm ist aufgetreten. Zeit: 29.03.2016 09:51:44 Anlage: #Anlage# Regler: #Regler# Alarmgrund: Alarm gehend; Temp.Grenzwert Device Location: K11_SM_Überhitzung Wert: NORMAL Alarmart: Critical ----------------------- gesendet von Centraline Arena Copyright © 2006..2008, Honeywell 2.1.0.170 alarm-id: eefc8bbe-97be-438e-ae37-f4be94354b40 destination-id: 025adbc6-be4d-4df3-bb65-6360857e7bbe

1 0

[Paradm] Critical Alarm ist aufgetreten in der LiegenschaftINS Uni Bonn Himalaya am 29.03.2016 09:51:44;
by klima＠ins.uni-bonn.de 29 Mar '16

29 Mar '16

Ein Critical Alarm ist aufgetreten. Zeit: 29.03.2016 09:51:44 \Liegenschaft: INS Uni Bonn Himalaya Regler: INS_KAELTE_1 Grund: Alarm gehend; Temp.Grenzwert Datenpunkt: K11_SM_Überhitzung Wert: NORMAL Alarmart: Critical ----------------------- gesendet von Centraline Arena Copyright © 2006..2008, Honeywell 2.1.0.170 alarm-id: eefc8bbe-97be-438e-ae37-f4be94354b40 destination-id: e3861b7a-be20-4b4f-8f65-853d8fe56bf8

1 0

[Paradm] Critical Alarm ist aufgetreten in der LiegenschaftINS Uni Bonn Himalaya am 29.03.2016 09:49:22;
by klima＠ins.uni-bonn.de 29 Mar '16

29 Mar '16

Ein Critical Alarm ist aufgetreten. Zeit: 29.03.2016 09:49:22 \Liegenschaft: INS Uni Bonn Himalaya Regler: INS_KAELTE_1 Grund: Alarm kommend; Temp.Grenzwert Datenpunkt: K11_SM_Überhitzung Wert: STÖR. Alarmart: Critical ----------------------- gesendet von Centraline Arena Copyright © 2006..2008, Honeywell 2.1.0.170 alarm-id: 7f4fa281-9175-4383-b5de-504658f771c5 destination-id: e3861b7a-be20-4b4f-8f65-853d8fe56bf8

1 0

[Paradm] Arena Alarm
by klima＠ins.uni-bonn.de 29 Mar '16

29 Mar '16

Ein Critical Alarm ist aufgetreten. Zeit: 29.03.2016 09:49:22 Anlage: #Anlage# Regler: #Regler# Alarmgrund: Alarm kommend; Temp.Grenzwert Device Location: K11_SM_Überhitzung Wert: STÖR. Alarmart: Critical ----------------------- gesendet von Centraline Arena Copyright © 2006..2008, Honeywell 2.1.0.170 alarm-id: 7f4fa281-9175-4383-b5de-504658f771c5 destination-id: 025adbc6-be4d-4df3-bb65-6360857e7bbe

1 0

[Paradm] Critical Alarm ist aufgetreten in der LiegenschaftINS Uni Bonn Himalaya am 29.03.2016 09:45:08;
by klima＠ins.uni-bonn.de 29 Mar '16

29 Mar '16

Ein Critical Alarm ist aufgetreten. Zeit: 29.03.2016 09:45:08 \Liegenschaft: INS Uni Bonn Himalaya Regler: INS_KAELTE_2 Grund: Alarm gehend; Temp.Grenzwert Datenpunkt: K21_SM_Überhitzung Wert: NORMAL Alarmart: Critical ----------------------- gesendet von Centraline Arena Copyright © 2006..2008, Honeywell 2.1.0.170 alarm-id: 036aa214-b6cd-44a1-9e3e-57c45c993550 destination-id: e3861b7a-be20-4b4f-8f65-853d8fe56bf8

1 0