Re: extract the process arguments from the crashdump
Hello, On 14.05.2018 18:12, Konstantin Belousov wrote: On Mon, May 14, 2018 at 05:32:21PM +0500, Eugene M. Zheganin wrote: Well, unfortunately this gives me exactly same information as the core.X.txt file contains - process names without arguments, and I really want to know what arguments ctladm had when the system has crashed: Most likely the in-kernel cache for the process arguments was dropped. Is there anything I can do to prevent this from happening, so if the system will crash next time I will get processes arguments extractable (in this case I would still like to get the arguments information) ? Thanks. Eugene. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: extract the process arguments from the crashdump
On Mon, May 14, 2018 at 05:32:21PM +0500, Eugene M. Zheganin wrote: > Hello, > > On 14.05.2018 16:15, Konstantin Belousov wrote: > > On Mon, May 14, 2018 at 01:02:28PM +0500, Eugene M. Zheganin wrote: > >> Hello, > >> > >> > >> Is there any way to extract the process arguments from the system > >> crashdump ? If yes, could anyone please explain to me how do I do it. > > ps -M vmcore.file -N /boot/mykernel/kernel -auxww > > Well, unfortunately this gives me exactly same information as the > core.X.txt file contains - process names without arguments, and I really > want to know what arguments ctladm had when the system has crashed: Most likely the in-kernel cache for the process arguments was dropped. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: extract the process arguments from the crashdump
Hello, On 14.05.2018 16:15, Konstantin Belousov wrote: On Mon, May 14, 2018 at 01:02:28PM +0500, Eugene M. Zheganin wrote: Hello, Is there any way to extract the process arguments from the system crashdump ? If yes, could anyone please explain to me how do I do it. ps -M vmcore.file -N /boot/mykernel/kernel -auxww Even if I ask ps explicitely to give me args, for some reason it ignores the format and 'args' keyword seems to be an alias for 'comm', but with square brackets: [root@san1:esx/r332096M]# ps -M vmcore.4 -N /boot/kernel/kernel -axo 'pid,ppid,comm,args' PID PPID COMMANDCOMMAND 0 0 kernel [kernel] 1 0 init [init] 2 0 crypto [crypto] 3 0 crypto returns [crypto returns] 4 0 cam[cam] 5 0 soaiod1[soaiod1] 6 0 soaiod2[soaiod2] 7 0 soaiod3[soaiod3] 8 0 soaiod4[soaiod4] 9 0 zfskern[zfskern] 10 0 audit [audit] 11 0 idle [idle] 12 0 intr [intr] 13 0 geom [geom] 14 0 usb[usb] 15 0 sctp_iterator [sctp_iterator] 16 0 pf purge [pf purge] 17 0 rand_harvestq [rand_harvestq] 18 0 enc_daemon0[enc_daemon0] 19 0 enc_daemon1[enc_daemon1] 20 0 enc_daemon2[enc_daemon2] 21 0 g_mirror swap [g_mirror swap] 22 0 pagedaemon [pagedaemon] 23 0 vmdaemon [vmdaemon] 24 0 pagezero [pagezero] 25 0 bufdaemon [bufdaemon] 26 0 bufspacedaemon [bufspacedaemon] 27 0 syncer [syncer] 28 0 vnlru [vnlru] 114 1 adjkerntz [adjkerntz] 593 1 moused [moused] 606 1 devd [devd] 701 1 syslogd[syslogd] 784 1 watchdogd [watchdogd] 866 0 ctl[ctl] 868 1 ctld [ctld] 894 1 zabbix_agentd [zabbix_agentd] 898 894 zabbix_agentd [zabbix_agentd] 901 894 zabbix_agentd [zabbix_agentd] 905 894 zabbix_agentd [zabbix_agentd] 907 894 zabbix_agentd [zabbix_agentd] 949 1 ntpd [ntpd] 968 1 nginx [nginx] 978 0 ng_queue [ng_queue] 1069 1 sshd [sshd] 1151 1 sendmail [sendmail] 1154 1 sendmail [sendmail] 1158 1 cron [cron] 1197 1 bsnmpd [bsnmpd] 1200 1 blacklistd [blacklistd] 1210 1 getty [getty] 1211 1 getty [getty] 1212 1 getty [getty] 1213 1 getty [getty] 1214 1 getty [getty] 1215 1 getty [getty] 1216 1 getty [getty] 1217 1 getty [getty] 1218 1 getty [getty] 12970 968 nginx [nginx] 12971 968 nginx [nginx] 12972 968 nginx [nginx] 12973 968 nginx [nginx] 12974 968 nginx [nginx] 12975 968 nginx [nginx] 12976 968 nginx [nginx] 12977 968 nginx [nginx] 12978 968 nginx [nginx] 12979 968 nginx [nginx] 12980 968 nginx [nginx] 12981 968 nginx [nginx] 12982 968 nginx [nginx] 12983 968 nginx [nginx] 12984 968 nginx [nginx] 12985 968 nginx [nginx] 12986 968 nginx [nginx] 32835 1069 sshd [sshd] 32884 32835 sshd [sshd] 32885 32884 zsh[zsh] 32929 32885 su [su] 32948 32929 csh[csh] 32964 32948 sh [sh] 32965 32964 mc [mc] 32966 32965 csh[csh] 48747 67993 sudo [sudo] 48750 67988 sudo [sudo] 48757 48750 zfs[zfs] 48758 48747 zfs[zfs] 48759 67990 sudo [sudo] 48762 48759 zfs[zfs] 48765 67997 sudo [sudo] 48766 48765 zfs[zfs] 48769 67984 sudo [sudo] 48770 48769 zfs[zfs] 48771 67996 sudo [sudo] 48772 48771 zfs[zfs] 48785 67991 sudo [sudo] 48786 48785 ctladm [ctladm] 48787 67983 sudo [sudo] 48788 48787 ctladm [ctladm] 48789 67986 sudo [sudo] 48790 48789 ctladm [ctladm] 48791 67985 sudo [sudo] 48792 48791 ctladm [ctladm] 48796 67987 sudo [sudo] 48797 48796 zfs[zfs] 67980 1 uwsgi [uwsgi] 67981 67980 uwsgi [uwsgi] 67982 67980 uwsgi [uwsgi] 67983 67980 uwsgi [uwsgi] 67984 67980 uwsgi [uwsgi] 67985 67980 uwsgi [uwsgi] 67986 67980 uwsgi [uwsgi] 67987 67980 uwsgi [uwsgi] 67988 67980 uwsgi [uwsgi] 67989 67980 uwsgi [uwsgi] 67990 67980 uwsgi [uwsgi] 67991 67980 uwsgi [uwsgi] 67992 67980 uwsgi [uwsgi] 67993 67980 uwsgi [uwsgi] 67994 67980 uwsgi [uwsgi] 67995 67980 uwsgi [uwsgi] 67996
Re: extract the process arguments from the crashdump
Hello, On 14.05.2018 16:15, Konstantin Belousov wrote: On Mon, May 14, 2018 at 01:02:28PM +0500, Eugene M. Zheganin wrote: Hello, Is there any way to extract the process arguments from the system crashdump ? If yes, could anyone please explain to me how do I do it. ps -M vmcore.file -N /boot/mykernel/kernel -auxww Well, unfortunately this gives me exactly same information as the core.X.txt file contains - process names without arguments, and I really want to know what arguments ctladm had when the system has crashed: [root@san1:esx/r332096M]# ps -M vmcore.4 -N /boot/kernel/kernel -auxww USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND root 0 0,0 0,0 0 0 - DLs 1янв.70 2866:37,17 [kernel] root 1 0,0 0,0542416 - DLs 1янв.70 0:03,95 [init] root 2 0,0 0,0 0 0 - DL1янв.70 0:00,00 [crypto] root 3 0,0 0,0 0 0 - DL1янв.70 0:00,00 [crypto returns] root 4 0,0 0,0 0 0 - RL1янв.70 175:44,92 [cam] root 5 0,0 0,0 0 0 - DL1янв.70 0:00,07 [soaiod1] root 6 0,0 0,0 0 0 - DL1янв.70 0:00,07 [soaiod2] root 7 0,0 0,0 0 0 - DL1янв.70 0:00,07 [soaiod3] root 8 0,0 0,0 0 0 - DL1янв.70 0:00,07 [soaiod4] root 9 0,0 0,0 0 0 - DL1янв.70 181:27,20 [zfskern] root 10 0,0 0,0 0 0 - DL1янв.70 0:00,00 [audit] root 11 0,0 0,0 0 0 - RL1янв.70 183810:56,57 [idle] root 12 0,0 0,0 0 0 - WL1янв.70 131:37,76 [intr] root 13 0,0 0,0 0 0 - DL1янв.70 1:33,61 [geom] root 14 0,0 0,0 0 0 - DL1янв.70 0:36,74 [usb] root 15 0,0 0,0 0 0 - DL1янв.70 0:00,00 [sctp_iterator] root 16 0,0 0,0 0 0 - DL1янв.70 1:38,61 [pf purge] root 17 0,0 0,0 0 0 - DL1янв.70 1:11,87 [rand_harvestq] root 18 0,0 0,0 0 0 - DL1янв.70 0:00,37 [enc_daemon0] root 19 0,0 0,0 0 0 - DL1янв.70 0:00,38 [enc_daemon1] root 20 0,0 0,0 0 0 - DL1янв.70 0:05,20 [enc_daemon2] root 21 0,0 0,0 0 0 - DL1янв.70 1:03,00 [g_mirror swap] root 22 0,0 0,0 0 0 - DL1янв.70 10:19,64 [pagedaemon] root 23 0,0 0,0 0 0 - DL1янв.70 0:18,40 [vmdaemon] root 24 0,0 0,0 0 0 - DL1янв.70 0:00,01 [pagezero] root 25 0,0 0,0 0 0 - DL1янв.70 0:01,71 [bufdaemon] root 26 0,0 0,0 0 0 - DL1янв.70 0:01,95 [bufspacedaemon] root 27 0,0 0,0 0 0 - DL1янв.70 2:20,07 [syncer] root 28 0,0 0,0 0 0 - DL1янв.70 0:03,19 [vnlru] root 114 0,0 0,06288 0 - DWs - 0:00,00 [adjkerntz] root 593 0,0 0,06600 1860 - Ds1янв.70 0:00,00 [moused] root 606 0,0 0,09180 620 - Ds1янв.70 0:07,76 [devd] root 701 0,0 0,06420 1928 - Ds1янв.70 0:26,92 [syslogd] root 784 0,0 0,03564 3612 - Ds1янв.70 0:01,46 [watchdogd] root 866 0,0 0,0 0 0 - DL1янв.70 42:20,99 [ctl] root 868 0,0 0,0 224200 2248 - Ds1янв.70 20:03,85 [ctld] zabbix 894 0,0 0,0 12424 0 - DW - 0:00,00 [zabbix_agentd] zabbix 898 0,0 0,0 12424 4504 - D 1янв.70 1:02,34 [zabbix_agentd] zabbix 901 0,0 0,0 12424 0 - DW - 0:00,00 [zabbix_agentd] zabbix 905 0,0 0,0 12424 1580 - D 1янв.70 3:03,14 [zabbix_agentd] zabbix 907 0,0 0,0 12424 1376 - D 1янв.70 3:05,45 [zabbix_agentd] root 949 0,0 0,0 12452 12532 - Ds1янв.70 0:19,90 [ntpd] root 968 0,0 0,0 1063848 0 - DWs - 0:00,00 [nginx] root 978 0,0 0,0 0 0 - DL1янв.70 0:00,00 [ng_queue] root1069 0,0 0,0 12848 3780 - Ds1янв.70 0:06,33 [sshd] root1151 0,0 0,0 10452 4304 - Ds1янв.70 0:09,25 [sendmail] smmsp 1154 0,0 0,0 10452 0 - DWs - 0:00,00 [sendmail] root1158 0,0 0,06464 0 - DWs - 0:00,00 [cron] root1197 0,0 0,0 10060 5268 - Ds1янв.70 4:51,59 [bsnmpd] root1200 0,0 0,06600 2112 - Ds1янв.70 0:04,13 [blacklistd] root1210 0,0 0,06408 1844 - Ds+ 1янв.70 0:00,00 [getty] root1211 0,0 0,06408 1844 - Ds+ 1янв.70 0:00,00 [getty] root1212 0,0 0,06408 1844 - Ds+ 1янв.70 0:00,00 [getty] root1213 0,0 0,06408 1844 - Ds+ 1янв.70 0:00,00 [getty] root1214 0,0 0,06408 1844 - Ds+ 1янв.70 0:00,00 [getty] root1215 0,0 0,0
Re: extract the process arguments from the crashdump
On Mon, May 14, 2018 at 01:02:28PM +0500, Eugene M. Zheganin wrote: > Hello, > > > Is there any way to extract the process arguments from the system > crashdump ? If yes, could anyone please explain to me how do I do it. ps -M vmcore.file -N /boot/mykernel/kernel -auxww ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
extract the process arguments from the crashdump
Hello, Is there any way to extract the process arguments from the system crashdump ? If yes, could anyone please explain to me how do I do it. Thanks. Eugene. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
