Logfile Errors

[jhesch]

Hello,

I am getting the following in my logfiles

<05/11/01@22:27:07> [main] opening source socket
<05/11/01@22:27:07> [main] source thread starting
<05/11/01@22:27:07> [source] listening for connection on port 8001
<05/11/01@22:27:07> [main] opening client socket
<05/11/01@22:27:07> [main] Client Stream thread [0] starting
<05/11/01@22:27:07> [main] client main thread starting
<05/11/01@22:27:23> [main] SIGHUP; Flushing Log File
<05/11/01@22:27:23> [main] SIGHUP handled. lost terminal
<05/11/01@22:27:23> [main] SIGHUP; Flushing Log File
<05/11/01@22:27:23> [main] SIGHUP; Flushing Log File
<05/11/01@22:27:23> [main] SIGHUP; Flushing Log File


And then nothing else gets written to the file. I can view the taillog file and it looks fine but the full logfile stops at this point.

Any ideas?

Thanks.

John

[naitsirch]

Hi,

I have the same question. In my log I have something like this:

<06/11/12@06:30:32> [dest: xxx.xxx.xxx.xxx] connection closed (1786 seconds) (UID: 23)[L: 1]{Bytes: 28561486}(P: 0)
<06/11/12@13:52:22> [main] SIGHUP; Flushing Log Files
<06/11/12@19:21:39> [dest: xxx.xxx.xxx.xxx] connection closed (50459 seconds) (UID: 21)[L: 0]{Bytes: 805043870}(P: 2)
<06/11/12@19:50:58> [dest: xxx.xxx.xxx.xxx] starting stream (UID: 24)[L: 1]{A: WinampMPEG/5.62, Ultravox/2.1}(P: 0)

What does "SIGHUP; Flushing Log Files" mean?

[DrO]

it's normal to see a message like that usually once a day (or if it's not had any connections, as soon as one happens and it has been over a day since the last rotation) as the DNAS (irrespective of the version used) will rotate it's log files to keep them down to a manageable size.

also please check the date of posts before adding to them as you've managed to bump an 11 year old thread.

-daz

[naitsirch]

Thanks for your answer.

I used this thread because I found it when I used Google to search for the log entry. And I didn't want to create a new thread.