New syslog file started every morning

[Former Member]

Hi Gurus,

In our 4.5B production system(no app servers), in SM21 there is a anew syslog file started every morning around 7:30. This was not the case before.

In our QA system which has identical rslg parameters - rslg/max_diskspace/local and others, this problem is not there.

The entries are also not too much. This cant be because too many entries are filling up the logfile evryday.

Did anyone see a problem like this before?

Thanks

Cyrus

[Former Member]

If I delete this job, will the logs be written normally?

Or, I have to do something else?

[Former Member]

Hi Sidhesh,

You are right on the money here. I found a delete_system_log job in sm37.

It was not easy to find it though. I had to select jobs without start date and jobs with previous jobs in more options to get tgis one. It only shows in scheduled list and no previous successful runs.

The user is pageone which is a standard user used by our developers.

Here are the steps in the job:

No. Program name/command Ext. Pgm. List Parameters User

1 RSSLGK90 1 - DELETE PAGEONE

2 RSSLGK90 2 - DELETE PAGEONE

3 RSSLGK90 3 - DELETE PAGEONE

4 RSSLGK90 4 - DELETE PAGEONE

5 RSSLGK90 5 - DELETE PAGEONE

6 RSSLGK90 6 - DELETE PAGEONE

7 RSSLGK90 7 - DELETE PAGEONE

8 RSSLGK90 8 - DELETE PAGEONE

9 RSSLGK90 9 - DELETE PAGEONE

10 RSSLGK90 10 - DELETE PAGEONE

11 RSSLGK90 11 - DELETE PAGEONE

12 RSSLGK90 12 - DELETE PAGEONE

13 RSSLGK90 13 - DELETE PAGEONE

14 RSSLGK90 14 - DELETE PAGEONE

15 RSSLG200 PAGEONE

What can i do to change this and bring it to a normal setting?

Thanks

Cyrus

[former_member185954]

Hi Cyrus,

Maybe the job is event triggered, please check for event triggered jobs in SM37

Regards,

Siddhesh

[Former Member]

Hello Cyrus,

this sounds like the problem of parameter records in the syslog as described in <a href="http://service.sap.com/sap/support/notes/48325">note 48325</a>.

Regards, Michael

[former_member185954]

Hi Cyrus,

Also there could be a parameter rslg/send_daemon_autostart which affects the system log and restarts it.

Leave the parameter rslg/send_daemon_autostart set to 0

Regards,

Siddhesh

[Former Member]

Are the traces enabled by any chances which will write the logs very frequently.. Check that

Thanks

Prince

[Former Member]

Here it is:

07:21:43 BTC 8 000 DDIC E00 S New system log file started with number 3508

07:31:26 DIA 1 000 SAPCOMM E01 S Program Z_ERDT02 started: Jvariant:

07:31:27 DIA 1 000 SAPCOMM E02 S Program Z_ERDT02 ended: Jvariant:

08:31:25 DIA 0 000 SAPCOMM E01 S Program Z_ERDT02 started: Jvariant:

08:31:27 DIA 0 000 SAPCOMM E02 S Program Z_ERDT02 ended: Jvariant:

08:55:16 DP Q0I K Operating system call recv failed (error no. 73 )

08:55:16 DP Q04 K User 11440 (STACO01 ), terminal 100 (CSTACOM ) disconnected

09:15:17 DP Q0G K Request (type NOWP) cannot be processed

09:30:16 DP Q0G K Request (type NOWP) cannot be processed

09:32:09 DIA 0 000 SAPCOMM E01 S Program Z_ERDT02 started: Jvariant:

09:32:10 DIA 0 000 SAPCOMM E02 S Program Z_ERDT02 ended: Jvariant:

09:45:16 DP Q0G K Request (type NOWP) cannot be processed

10:00:16 DP Q0G K Request (type NOWP) cannot be processed

10:03:17 DIA 15 271 SEIB14 ZSCM R68 W Perform rollback

10:03:17 DIA 15 271 SEIB14 ZSCM AB0 T Run-time error "DYNPRO_MSG_IN_HELP" occurred

10:03:18 DIA 15 271 SEIB14 ZSCM AB1 K > Short dump "070123 100317 debmu598 SEIB14 " generated

10:15:17 DP Q0G K Request (type NOWP) cannot be processed

10:30:16 DP Q0G K Request (type NOWP) cannot be processed

10:31:42 DIA 2 000 SAPCOMM E01 S Program Z_ERDT02 started: Jvariant:

10:31:43 DIA 2 000 SAPCOMM E02 S Program Z_ERDT02 ended: Jvariant:

10:40:18 BTC 3 000 OPTI R49 K Communication error, CPIC return code 027, SAP return code 456

10:40:18 BTC 3 000 OPTI R64 K > CPI-C function: CMINIT(SAP)

10:45:16 DP Q0G K Request (type NOWP) cannot be processed

11:00:16 DP Q0G K Request (type NOWP) cannot be processed

11:15:17 DP Q0G K Request (type NOWP) cannot be processed

11:24:06 SPO 51 000 SAPSYS FBM W The printer G20A was temporarily locked after a connection problem.

11:30:16 DP Q0G K Request (type NOWP) cannot be processed

11:31:43 DIA 2 000 SAPCOMM E01 S Program Z_ERDT02 started: Jvariant:

11:31:44 DIA 2 000 SAPCOMM E02 S Program Z_ERDT02 ended: Jvariant:

11:45:16 DP Q0G K Request (type NOWP) cannot be processed

11:49:03 SPO 51 000 SAPSYS FBM W The printer G20A was temporarily locked after a connection problem.

11:59:49 SPO 51 000 SAPSYS FBL W Printer G20A print request demand is too slow. (27 seconds)

12:00:16 DP Q0G K Request (type NOWP) cannot be processed

12:03:13 SPO 51 000 SAPSYS FBM W The printer G20A was temporarily locked after a connection problem.

12:08:54 SPO 51 000 SAPSYS FBM W The printer G20A was temporarily locked after a connection problem.

12:15:19 DP Q0G K Request (type NOWP) cannot be processed

12:30:16 DP Q0G K Request (type NOWP) cannot be processed

12:31:21 DIA 0 000 SAPCOMM E01 S Program Z_ERDT02 started: Jvariant:

12:31:23 DIA 0 000 SAPCOMM E02 S Program Z_ERDT02 ended: Jvariant:

12:45:16 DP Q0G K Request (type NOWP) cannot be processed

13:00:16 DP Q0G K Request (type NOWP) cannot be processed

13:15:17 DP Q0G K Request (type NOWP) cannot be processed

13:30:16 DP Q0G K Request (type NOWP) cannot be processed

13:45:16 DP Q0G K Request (type NOWP) cannot be processed

14:00:16 DP Q0G K Request (type NOWP) cannot be processed

14:15:17 DP Q0G K Request (type NOWP) cannot be processed

14:30:16 DP Q0G K Request (type NOWP) cannot be processed

14:45:16 DP Q0G K Request (type NOWP) cannot be processed

14:48:04 DIA 5 271 MITK01 ZRFC D01 K Transactions termination FS 551 ( 1729 2007 2200004102 )

14:48:04 DIA 5 271 MITK01 ZRFC R68 W Perform rollback

15:00:16 DP Q0G K Request (type NOWP) cannot be processed

15:01:06 DIA 0 271 JACK22 ZSCM D01 K Transactions termination ZCONTRACT _MSG 000 ( Please enter Contract review date )

15:01:06 DIA 0 271 JACK22 ZSCM R68 W Perform rollback

15:15:17 DP Q0G K Request (type NOWP) cannot be processed

15:30:17 DP Q0G K Request (type NOWP) cannot be processed

15:43:25 DIA 1 271 TAKA08 D01 K Transactions termination /CCITCTS/ PB_MESSAG ES001 ( TREEV_SIMPLE_ADD_NODES )

15:43:25 DIA 1 271 TAKA08 R68 W Perform rollback

15:45:16 DP Q0G K Request (type NOWP) cannot be processed

16:00:16 DP Q0G K Request (type NOWP) cannot be processed

16:00:27 DP Q0I K Operating system call recv failed (error no. 73 )

16:00:27 DP Q04 K User 11376 (BAYL02 ), terminal 95 (MBayliss ) disconnected

16:08:42 DIA 1 271 RANGA01 US1 X User RANGA01 locked due to incorrect logon

16:09:09 DIA 1 271 RANGA01 US3 X Logon attempt for locked user RANGA01

16:15:17 DP Q0G K Request (type NOWP) cannot be processed

16:18:51 DIA 1 271 IRELA02 /CCI R68 W Perform rollback

[former_member185954]

Hi Cyrus,

I had guessed it so... looks like the system log is scheduled in background. There is a way to schedule system log in background.

Someone must have scheduled this report RSLG0000, to execute periodically. Use SM37 to figure out who has scheduled that report RSLG0000

Check this link for what checking what I mean.

http://help.sap.com/saphelp_47x200/helpdata/en/69/0b0904b14d11d299780000e83dd9fc/frameset.htm

Regards,

Siddhesh

[former_member185954]

hi can you post the system log ?