1 |
On Thu, May 13, 2021 at 12:20 AM Walter Dnes <waltdnes@××××××××.org> wrote: |
2 |
> |
3 |
> On Wed, May 12, 2021 at 09:50:29PM -0500, Dale wrote |
4 |
> > Walter Dnes wrote: |
5 |
> > > On Wed, May 12, 2021 at 11:16:56AM -0700, Mark Knecht wrote |
6 |
> > >> Is there nothing in the system logs? What's near the end before |
7 |
whatever |
8 |
> > >> you get from booting after this issue? |
9 |
> > > Where would those logfiles be? "dmesg" starts off with... |
10 |
> > > |
11 |
> > |
12 |
> > |
13 |
> > Most likely in /var/log/messages. The bad thing about dmesg, I think it |
14 |
> > resets when rebooting which erases previous info. |
15 |
> > |
16 |
> > As Mark pointed out, you need to go back to the time before it starts |
17 |
> > adding the boot up process. |
18 |
> |
19 |
> No help. /var/log/messages goes straight from iptables messages to |
20 |
> bootup with no indication of shutdown... |
21 |
> |
22 |
> May 12 11:26:31 i3 kernel: FECESBOOK:IN= OUT=eth0 SRC=192.168.1.249 |
23 |
DST=31.13.80.12 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=5824 DF PROTO=TCP |
24 |
SPT=50566 DPT=443 WINDOW=64170 RES=0x00 SYN URGP=0 |
25 |
> May 12 11:26:32 i3 kernel: FECESBOOK:IN= OUT=eth0 SRC=192.168.1.249 |
26 |
DST=31.13.80.12 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=60152 DF PROTO=TCP |
27 |
SPT=50568 DPT=443 WINDOW=64170 RES=0x00 SYN URGP=0 |
28 |
> May 12 11:34:04 i3 syslog-ng[1384]: syslog-ng starting up; |
29 |
version='3.30.1' |
30 |
> May 12 11:34:04 i3 crond[1414]: /usr/sbin/crond 4.5 dillon's cron daemon, |
31 |
started with loglevel notice |
32 |
> May 12 11:34:04 i3 /usr/sbin/gpm[1443]: *** info [daemon/startup.c(136)]: |
33 |
> May 12 11:34:04 i3 /usr/sbin/gpm[1443]: Started gpm successfully. Entered |
34 |
daemon mode. |
35 |
> |
36 |
> When doing a regular shutdown I get stuff like... |
37 |
> |
38 |
> May 12 11:42:31 i3 shutdown[1974]: shutting down for system reboot |
39 |
> May 12 11:42:31 i3 init[1]: Switching to runlevel: 6 |
40 |
> May 12 11:42:32 i3 init[1]: Trying to re-exec init |
41 |
> May 12 11:42:32 i3 start-stop-daemon[2053]: Will stop /usr/sbin/sshd |
42 |
> May 12 11:42:32 i3 start-stop-daemon[2053]: Will stop PID 1764 |
43 |
> May 12 11:42:32 i3 start-stop-daemon[2053]: Sending signal 15 to PID 1764 |
44 |
> May 12 11:42:32 i3 sshd[1764]: Received signal 15; terminating. |
45 |
> |
46 |
|
47 |
OK, but those messages are yesterday, May 12th, at 11:42 in the morning. |
48 |
Being that you started this thread on May 12th at 9:35 (when I received the |
49 |
first email anyway) the actual lockup presumably occurred earlier. |
50 |
|
51 |
I believe you're in the correct file, or set of files. Depending on how |
52 |
your logging works (what logger, what options) generally the logs roll over |
53 |
into successive files. (*.1, *.2, *.3, etc) Assuming you have some idea |
54 |
when the lockup occurred you want to look for what was going on just before |
55 |
that. Do the logs hit a date/time and stop? Or do they go on logging with |
56 |
lots of similar or repeating messages for hours or days? |
57 |
|
58 |
Do double check that you log into a directory that doesn't run out of space |
59 |
once a month. That could cause problems also. |
60 |
|
61 |
HTH, |
62 |
MArk |