Technical Forum
Ask questions. Discover Answers.
cancel
Showing results for 
Search instead for 
Did you mean: 

Configuration reload request received, reloading configuration

rajeev_81179
Nimbostratus
Nimbostratus
Service: syslog-ng (1233)

 

Event: Configuration reload request received, reloading configuration

 

I did not manually relaod the config, but this message is in my system log.

 

 

Tried looking in F5 database, what exactly do u suggest I do, just wait for the service to restart or reload the LTM ????

 

 

10 REPLIES 10

hooleylist
Cirrostratus
Cirrostratus
Was this at 4am? It's likely syslog-ng was re-initialized as part of cronjobs that run each morning:

 

 

Oct 2 04:02:03 host syslog-ng[1682]: Configuration reload request received, reloading configuration;

 

 

It's nothing to worry about.

 

 

Aaron

rajeev_81179
Nimbostratus
Nimbostratus
thanks a lot aaron...

 

You are a star....

Matt_112326
Historic F5 Account
Maybe logrotate?

Simon_Sparks_12
Nimbostratus
Nimbostratus

This occurred at 4:02am for me but also during the day at 11:46am which caused an interruption in the availability of the REST API in v11.4.

 

ekintulga_15690
Nimbostratus
Nimbostratus

Do devices get into "changes pending" state after this operation?

 

HI Dear,

 

https://support.f5.com/kb/en-us/solutions/public/11000/600/sol11633

 

The BIG-IP system runs a daily log rotation script at 4:02 A.M. that reloads the syslog-ng process. As a result, the system logs a message similar to the following example to the /var/log/messages file at that time:

 

syslog-ng[]: Configuration reload request received, reloading configuration;

 

 

In the log message example, note the following:

 

In my case yes. Change pending is there

I have the same issue. I can see the log on var/ log/messages but we never start the device and device uptime is since long time

nitass
F5 Employee
F5 Employee

Do devices get into "changes pending" state after this operation?

i do not think so.

e.g.

[root@ve11a:Active:In Sync] config  date; tmsh show cm sync-status
Mon Jul  7 07:36:05 PDT 2014

------------------------------------------------------------------------------------------
CM::Sync Status
------------------------------------------------------------------------------------------
Color    green
Status   In Sync
Summary  All devices in the device group are in sync
Details
         /Common/ve11b.acme.local: connected (for 521240 seconds)
         /Common/ve11c.acme.local: connected (for 521240 seconds)
         /Common/device_trust_group (In Sync): All devices in the device group are in sync
         /Common/dg (In Sync): All devices in the device group are in sync

[root@ve11a:Active:In Sync] config  date;/etc/init.d/syslog-ng reload
Mon Jul  7 07:36:20 PDT 2014

[root@ve11a:Active:In Sync] config  cat /var/log/messages
Jul  7 07:36:20 ve11a notice syslog-ng[27803]: Configuration reload request received, reloading configuration;

[root@ve11a:Active:In Sync] config  date; tmsh show cm sync-status
Mon Jul  7 07:36:35 PDT 2014

------------------------------------------------------------------------------------------
CM::Sync Status
------------------------------------------------------------------------------------------
Color    green
Status   In Sync
Summary  All devices in the device group are in sync
Details
         /Common/ve11b.acme.local: connected (for 521240 seconds)
         /Common/ve11c.acme.local: connected (for 521240 seconds)
         /Common/device_trust_group (In Sync): All devices in the device group are in sync
         /Common/dg (In Sync): All devices in the device group are in sync

ekintulga_15690
Nimbostratus
Nimbostratus

Thanks nitass, yes it doesn't correlate with the times changes performed. I tested here as well. Thanks for your answer.

 

nice commands indeed.

 

gurulee_340176
Altostratus
Altostratus

We just had our Skype virtual servers go down in F5 and Skype clients disconnected. At this time I saw this message as well. We also had a changes pending state with sync partner as well afterwards. Are we sure it does not cause an interruption in connectivity?