Re: dhcp server returns core dump when i define network with mask 8
On 23/07/2013 09:03, jb wrote:
s m sam.gh1986 at gmail.com writes:
...
subnet 192.0.0.0 netmask 255.0.0.0 {
range 192.0.0.1 192.255.255.255;
The 'range' denotes IP addresses that can be allocated to clients.
The IP 192.255.255.255 is a reserved broadcast address for the network.
jb
It's definitely bad idea to try to use it, but it doesn't explain the
core dump.
Also, using DHCP to dish out addresses that don't belong to you AND
aren't on a private network (as defined by IANA) will probably lead to
trouble. Valid private address ranges are:
10.0.0.0 - 10.255.255.255 (private class A)
172.16.0.0 - 172.31.255.255 (private class B x 16)
192.168.0.0 - 192.168.255.255 (private class C x 256)
Which block you use is really a matter of taste - classes haven't been
used in routing for quite a while so you can consider them all as
straight blocks but I (for one) still treat them as classed just to help
me visualise what's what. For example, I'll use one class C per site to
prevent conflicts over VPN.
192.0.0.0/24 addresses are allocated to real hosts on the wider
internet, although IIRC some of the lower ones are reserved for use in
documentation (like example.com) - is that where the idea came from?!? :-)
Regards, Frank.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: dhcp server returns core dump when i define network with mask 8
thanks Frank,
192 is just a sample. if i want to define 125.0.0.0 netmask 255.0.0.0, dhcp
server core dump either. you're right, it is better to use just some
limited addresses to avoid possible troubles. but i want to run my dhcp
server for all possible networks.
now my question is: if i define a network with mask 8, the rang should be
like: 126.0.0.0 126.254.255.255?
and thank you jb but if i define my network like below, server runs
correctly:
log-facility local7;
subnet 192.168.0.0 netmask 255.255.0.0 {
range 192.168.0.1 192.168.255.255;
}
i think 192.168.255.55 is reserved for broadcast too. is it not true? if
yes, why dhcp server works correctly?
please help me to clear my mind.
regards,
SAM
On Tue, Jul 23, 2013 at 12:56 PM, Frank Leonhardt fra...@fjl.co.uk wrote:
On 23/07/2013 09:03, jb wrote:
s m sam.gh1986 at gmail.com writes:
...
subnet 192.0.0.0 netmask 255.0.0.0 {
range 192.0.0.1 192.255.255.255;
The 'range' denotes IP addresses that can be allocated to clients.
The IP 192.255.255.255 is a reserved broadcast address for the network.
jb
It's definitely bad idea to try to use it, but it doesn't explain the
core dump.
Also, using DHCP to dish out addresses that don't belong to you AND aren't
on a private network (as defined by IANA) will probably lead to trouble.
Valid private address ranges are:
10.0.0.0 - 10.255.255.255 (private class A)
172.16.0.0 - 172.31.255.255 (private class B x 16)
192.168.0.0 - 192.168.255.255 (private class C x 256)
Which block you use is really a matter of taste - classes haven't been
used in routing for quite a while so you can consider them all as straight
blocks but I (for one) still treat them as classed just to help me
visualise what's what. For example, I'll use one class C per site to
prevent conflicts over VPN.
192.0.0.0/24 addresses are allocated to real hosts on the wider internet,
although IIRC some of the lower ones are reserved for use in documentation
(like example.com) - is that where the idea came from?!? :-)
Regards, Frank.
__**_
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/**mailman/listinfo/freebsd-**questionshttp://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-**
unsubscr...@freebsd.org freebsd-questions-unsubscr...@freebsd.org
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: dhcp server returns core dump when i define network with mask 8
Quoting Frank Leonhardt fra...@fjl.co.uk: There are two common ways of defining a subnet mask - one is a dotted quad (e.g. 255.255.255.0) and the other is with a slash and the number of low-order bits - e.g. 192.168.1.0/8. Eight bits here means you get 2^8 addresses (i.e. 256). Don't use the first and last address in the range - the first is complicated (the network address) and the last is for broadcast packets. This doesn't always hold true but you're unlikely to come across exceptions. This is the wrong way round. the number after the slash indicates the number of bits in the network address - the high-order bits. So, when you say you want to define a network with mask 8 I don't really know what you mean from your example. Do you mean a /8? 192.168.1.0/8 = range 192.168.1.1192.168.1.254 with a subnet mask of 255.255.255.0 (0xFF00) Nope. 192.168.1.0/24 = 192.168.1.1-255 mask 255.255.255.0. 192.168.1.0/8 doesn't start where you think it does (and is arguably the wrong way to specify that network) because all but the first 8 bits are masked out - it's 192.0.0.0 - 192.255.255.255. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: dhcp server returns core dump when i define network with mask 8
s m sam.gh1986 at gmail.com writes:
and thank you jb but if i define my network like below, server runs
correctly:
log-facility local7;
subnet 192.168.0.0 netmask 255.255.0.0 {
range 192.168.0.1 192.168.255.255;
}
i think 192.168.255.55 is reserved for broadcast too. is it not true? if
yes, why dhcp server works correctly?
please help me to clear my mind.
regards,
SAM
Regarding subnets:
192.168.0.0 netmask 255.255.0.0
is equivalent to
192.168.0.0/16
which splits it into a network id 192.168. and host id .0.0
Another example:
192.168.0.0 netmask 255.0.0.0
is equivalent to
192.168.0.0/8
which splits it into a network id 192. and host id 168.0.0
Regarding broadcast address:
yes, for subnet 192.168.0.0/16 the broadcast ip is 192.168.255.255 .
What are the implications of including broadcast ip in range option ?
Firstly, it depends on how the authors of software, that is DHCP server,
interpreted the dhcpd.conf option data. They could have rejected that
option up front, or accept it (implying you are the boos !).
After all, dhcpd.conf(5) only says:
The range statement
range [ dynamic-bootp ] low-address [ high-address];
For any subnet on which addresses will be assigned dynamically, there
must be at least one range statement. The range statement gives
the lowest and highest IP addresses in a range. All IP addresses in
the range should be in the subnet in which the range statement is declared.
Well, looks good to me so far !
Next, dhcpd.conf(5) describes how DHCP server deals with:
DYNAMIC ADDRESS ALLOCATION
...
IP ADDRESS CONFLICT PREVENTION
...
You can analyse it and see if any trouble lurks there ...
Secondly, let's assume there was no problem and that ip was dispensed to a host.
But, in a different place of IP specs there is a RFC??? which says that
the 192.168.255.255 as a generically valid ip address will assume some
additional meaning, that is it will be treated as a broadcast address
(it will represent all hosts on a subnet).
Wow ! That should give you a pause ...
It is said that the broadcast address is used by an application to send
the same message to all other hosts in the network simultaneously.
Who is using it ?
Well, our client host is using it (let's assume it was assigned that ip
above ...).
What happens when the host sends a packet out with a source ip address of
a broadcast ip address ? One can imagine that the destination host will
respond and send back a packet to a destination ip address which is our
sender's broadcast ip address ... You mean to every host on that network ?
Something fishy is on the way ...
But while doing it, it will utilize some protocols, like ARP, RIP, etc.
In addition, it is said that broadcast messages are typically produced by
network protocols such as the Address Resolution Protocol (ARP) and
the Routing Information Protocol (RIP).
They will utilize that ip broadcast address regardless of the fact that it
has been presumably assigned to the client host too.
Wow, what a soup ...
Enjoy it while it lasts :-)
jb
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: dhcp server returns core dump when i define network with mask 8
On 23/07/2013 13:35, j.mcke...@ru.ac.za wrote: Quoting Frank Leonhardt fra...@fjl.co.uk: There are two common ways of defining a subnet mask - one is a dotted quad (e.g. 255.255.255.0) and the other is with a slash and the number of low-order bits - e.g. 192.168.1.0/8. Eight bits here means you get 2^8 addresses (i.e. 256). Don't use the first and last address in the range - the first is complicated (the network address) and the last is for broadcast packets. This doesn't always hold true but you're unlikely to come across exceptions. This is the wrong way round. the number after the slash indicates the number of bits in the network address - the high-order bits. So, when you say you want to define a network with mask 8 I don't really know what you mean from your example. Do you mean a /8? 192.168.1.0/8 = range 192.168.1.1192.168.1.254 with a subnet mask of 255.255.255.0 (0xFF00) Nope. 192.168.1.0/24 = 192.168.1.1-255 mask 255.255.255.0. 192.168.1.0/8 doesn't start where you think it does (and is arguably the wrong way to specify that network) because all but the first 8 bits are masked out - it's 192.0.0.0 - 192.255.255.255. Quite correct - for some reason I got that bit backwards when I'm using it every day the right way around. It's ludicrously hot and humid in London at the moment, lack of sleep caused thereby c... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
dhcp server returns core dump when i define network with mask 8
hello all,
i have a question about dhcpd in freebsd8.2 . when i define my network like
below in dhcpd.conf file, server doesn't run correctly and return core
dump
this is my dhcpd.conf file:
ddns-update-style none;
log-facility local7;
subnet 192.0.0.0 netmask 255.0.0.0 {
range 192.0.0.1 192.255.255.255;
}
i want to define a network with mask 8. is this config wrong? if yes, how
should i define it?
thanks in advance,
SAM
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: dhcp server returns core dump when i define network with mask 8
s m sam.gh1986 at gmail.com writes:
...
subnet 192.0.0.0 netmask 255.0.0.0 {
range 192.0.0.1 192.255.255.255;
The 'range' denotes IP addresses that can be allocated to clients.
The IP 192.255.255.255 is a reserved broadcast address for the network.
jb
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Daily periodic cronjob generates core dump
On Fri, Jun 14, 2013 at 2:48 PM, Greg Larkin glar...@freebsd.org wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 6/14/13 6:26 AM, C. L. Martinez wrote: Hi all, I have a FreeBSD 9.1 host (fully patched) with ZFS. Every day I am receiving in security output this message: fbsd.domain.local kernel log messages: +++ /tmp/security.AT1oDecp 2013-06-14 03:02:10.0 + +pid 75930 (try), uid 0: exited on signal 10 (core dumped) pid 76241 +(try), uid 0: exited on signal 10 (core dumped) How can I detect where is the problem?? Thanks. You can safely ignore this message, as it's generated by autotools when you are building your packages with poudriere. See: http://lists.freebsd.org/pipermail/freebsd-questions/2010-February/213026.html Also check section 12.11.3 on this page for more details on suppressing the message: http://www.freebsd.org/doc/en/books/handbook/configtuning-configfiles.html Many thanks Greg. Works. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Daily periodic cronjob generates core dump
Hi all, I have a FreeBSD 9.1 host (fully patched) with ZFS. Every day I am receiving in security output this message: fbsd.domain.local kernel log messages: +++ /tmp/security.AT1oDecp 2013-06-14 03:02:10.0 + +pid 75930 (try), uid 0: exited on signal 10 (core dumped) pid 76241 +(try), uid 0: exited on signal 10 (core dumped) How can I detect where is the problem?? Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Daily periodic cronjob generates core dump
C. L. Martinez writes: I have a FreeBSD 9.1 host (fully patched) with ZFS. Every day I am receiving in security output this message: fbsd.domain.local kernel log messages: +++ /tmp/security.AT1oDecp 2013-06-14 03:02:10.0 + +pid 75930 (try), uid 0: exited on signal 10 (core dumped) pid 76241 +(try), uid 0: exited on signal 10 (core dumped) How can I detect where is the problem?? Have you added anything to the default system crontab? Are there any user crontabs? Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Daily periodic cronjob generates core dump
On Fri, Jun 14, 2013 at 11:42 AM, Robert Huff roberth...@rcn.com wrote: C. L. Martinez writes: I have a FreeBSD 9.1 host (fully patched) with ZFS. Every day I am receiving in security output this message: fbsd.domain.local kernel log messages: +++ /tmp/security.AT1oDecp 2013-06-14 03:02:10.0 + +pid 75930 (try), uid 0: exited on signal 10 (core dumped) pid 76241 +(try), uid 0: exited on signal 10 (core dumped) How can I detect where is the problem?? Have you added anything to the default system crontab? Are there any user crontabs? Robert Huff I have added a script to rebuild packages every week with poudriere: # /etc/crontab - root's crontab for FreeBSD # # $FreeBSD: release/9.1.0/etc/crontab 194170 2009-06-14 06:37:19Z brian $ # SHELL=/bin/sh PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin # #minute hourmdaymonth wdaywho command # */5 * * * * root/usr/libexec/atrun # # Save some entropy so that /dev/random can re-seed on boot. */11* * * * operator /usr/libexec/save-entropy # # Rotate log files every hour, if necessary. 0 * * * * rootnewsyslog # # Perform daily/weekly/monthly maintenance. 1 3 * * * rootperiodic daily 15 4 * * 6 rootperiodic weekly 30 5 1 * * rootperiodic monthly # # Adjust the time zone if the CMOS clock keeps local time, as opposed to # UTC time. See adjkerntz(8) for details. 1,310-5 * * * rootadjkerntz -a # # Rebuild all necessary packages for SIEM infrastructure 35 23 * * 4 root/root/bin/build_pkgs all ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Daily periodic cronjob generates core dump
C. L. Martinez writes: Have you added anything to the default system crontab? Are I have added a script to rebuild packages every week with poudriere: And if you comment that out? Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Daily periodic cronjob generates core dump
On Fri, Jun 14, 2013 at 12:17 PM, Robert Huff roberth...@rcn.com wrote: C. L. Martinez writes: Have you added anything to the default system crontab? Are I have added a script to rebuild packages every week with poudriere: And if you comment that out? Robert Huff Uhmm .. I will try it ... but for what reason?? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Daily periodic cronjob generates core dump
Uhmm .. I will try it ... but for what reason?? It would be nice to see if anything else in the crontab might be causing it. You can also run `periodic security` as root and see if it manfiests the same way. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Daily periodic cronjob generates core dump
On Fri, Jun 14, 2013 at 12:30 PM, Jason Birch jbi...@jbirch.net wrote: Uhmm .. I will try it ... but for what reason?? It would be nice to see if anything else in the crontab might be causing it. You can also run `periodic security` as root and see if it manfiests the same way. Running from console, no problem: root@fbsd:~ # periodic security Checking setuid files and devices: Checking negative group permissions: Checking for uids of 0: root 0 toor 0 Checking for passwordless accounts: Checking login.conf permissions: Checking for ports with mismatched checksums: fbsd.domain.local pf denied packets: +++ /tmp/security.NiYRT5WC 2013-06-14 12:44:34.0 + +block drop in log quick on ! lo0 inet from 127.0.0.0/8 to any [ Evaluations: 166898 Packets: 0 Bytes: 0 States: 0 ] +block drop in log quick on ! em0 inet from 172.16.0.0/24 to any [ Evaluations: 132328 Packets: 0 Bytes: 0 States: 0 ] +block drop in log quick inet from 172.16.0.109 to any [ Evaluations: 132328 Packets: 0 Bytes: 0 States: 0 ] +block drop in log quick on ! lo0 inet6 from ::1 to any [ Evaluations: 132328 Packets: 0 Bytes: 0 States: 0 ] +block drop in log all [ Evaluations: 132328 Packets: 128574 Bytes: 12252183 States: 0 ] +block drop in log quick from ossec_fwtable to any [ Evaluations: 132328 Packets: 0 Bytes: 0 States: 0 ] +block drop out log quick from any to ossec_fwtable [ Evaluations: 166898 Packets: 0 Bytes: 0 States: 0 ] fbsd.domain.local login failures: fbsd.domain.local refused connections: -- End of security output -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
I just had a crash, core dump
My system 9.1-RELEASE ll /var/crash/ total 697996 -rw-r--r-- 1 root wheel 2 14 Mar 12:51 bounds -rw--- 1 root wheel 577047 14 Mar 12:52 core.txt.0 -rw--- 1 root wheel460 14 Mar 12:51 info.0 -rw-r--r-- 1 root wheel 5 4 Dec 10:34 minfree -rw--- 1 root wheel 784556032 14 Mar 12:52 vmcore.0 Who would be interested in this? /Leslie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: I just had a crash, core dump
2013-03-14 14:55, Damien Fleuriot skrev: On 14 Mar 2013, at 12:57, Leslie Jensen les...@eskk.nu wrote: My system 9.1-RELEASE ll /var/crash/ total 697996 -rw-r--r-- 1 root wheel 2 14 Mar 12:51 bounds -rw--- 1 root wheel 577047 14 Mar 12:52 core.txt.0 -rw--- 1 root wheel460 14 Mar 12:51 info.0 -rw-r--r-- 1 root wheel 5 4 Dec 10:34 minfree -rw--- 1 root wheel 784556032 14 Mar 12:52 vmcore.0 Who would be interested in this? /Leslie You, I assume ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Yes of course! Unfortunately I do not know what to do with this information. I thought that maybe it could be useful for someone working on development of FreeBSD. Thanks /Leslie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: I just had a crash, core dump
On Thu, Mar 14, 2013 at 3:45 PM, Leslie Jensen les...@eskk.nu wrote: 2013-03-14 14:55, Damien Fleuriot skrev: On 14 Mar 2013, at 12:57, Leslie Jensen les...@eskk.nu wrote: My system 9.1-RELEASE ll /var/crash/ total 697996 -rw-r--r-- 1 root wheel 2 14 Mar 12:51 bounds -rw--- 1 root wheel 577047 14 Mar 12:52 core.txt.0 -rw--- 1 root wheel460 14 Mar 12:51 info.0 -rw-r--r-- 1 root wheel 5 4 Dec 10:34 minfree -rw--- 1 root wheel 784556032 14 Mar 12:52 vmcore.0 Who would be interested in this? /Leslie You, I assume ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Yes of course! Unfortunately I do not know what to do with this information. I thought that maybe it could be useful for someone working on development of FreeBSD. Take a look at this[1] and try to extract a backtrace. Post it again to see if it catches the attention of a kernel hacker ;) Cheers [1] http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html Thanks /Leslie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
kernel panic leads to core dump
I was going ahead and attempting to install libreoffice 3.5.7 and it was going along nicely until the kernel panicked. When I rebooted, I tried to start the install again but it aborted so I went to make clean in /usr/ports/editors/libreoffice when the kernel panicked again. I have two of all the core dump files (one set from each). makeoptions DEBUG=-g# Build kernel with gdb(1) debug symbols Is already enabled in the generic (amd64) kernel. $ uname -a FreeBSD alex-laptop 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 -- Yours in Christ, Joseph A Nagy Jr Whoever loves instruction loves knowledge, But he who hates correction is stupid. -- Proverbs 12:1 Emails are not formal business letters, whatever businesses may want. Original content CopyFree (F) under the OWL http://owl.apotheon.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
ZendOptimizer - core dump
hi, I need to migrate application which uses ZendOptimizer. The system and packages installed are: 8.1-STABLE, apache-2.2.17_2, ZendOptimizer-3.3.0.a, mysql-client-5.5.10, php52-5.2.17, compat6x-amd64-6.4.604000.200810_3. When I run php -v it dumps core. any hints would be greatly appreciated. Has anybody success story running ZendOptimizer? (I read, the support of ZendOptimizer for FreeBSD has been dropped; therefore I cannot use php 5.3) Regards, lk ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
locale settings and core dump LyX
Hi, When I start LyX I'm getting an error: ... terminate called after throwing an instance of 'std::runtime_error' what(): locale::facet::_S_create_c_locale name not valid Abort (core dumped) ... This seems to have something to do with my locale settings: ... LANG=en_US.UTF-8 LC_CTYPE=en_US.UTF-8 LC_COLLATE=en_US.UTF-8 LC_TIME=en_US.UTF-8 LC_NUMERIC=en_US.UTF-8 LC_MONETARY=en_US.UTF-8 LC_MESSAGES=en_US.UTF-8 LC_ALL= ... When I change the locale setting to C, lyx runs fine, but I want to keep my locale at UTF-8. So how can I keep UTF-8 and keep using LyX? Thanks in advance, Marco -- QOTD: The only easy way to tell a hamster from a gerbil is that the gerbil has more dark meat. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: CYRUS IMAP cyradm core dump problem
Hello Reko Only for the records: I did realy a lot of tests in the past weeks (with and without security/heimdal, and also the kerberos base, etc.). The goal is, I was unable to get back to run with saslauthd -a kerberos5. The only way I found is to run saslauthd -a pam (but here you need also a patch, see under freebsd.org/send-pr.html). I'm now a bit frusting, because it's an import part of the base system and itdefinitly do not work. Regards, Am Mon, Oct 04, 2010 at 02:45:21PM +0300 Reko Turja schrieb: Am Thu, Sep 23, 2010 at 03:05:30PM +0300 Reko Turja schrieb: I applied the patch as suggested by Reko, but it seemed to make no difference After the patch recompiling and linking at least SASL is needed after buildworld and inatallation of new world. removing libgssapiv2 libs however, solved my cyradm problem will this cause issues into the future for any other ports I may need ti install ? Unless you need kerberos authentication at some point, removing the libs is non-issue. I'm running in the same situation as you (see http://www.freebsd.org/cgi/getmsg.cgi?fetch=846230+852662+/usr/local/www/db/text/2010/freebsd-stable/20101003.freebsd-stable). I did tried a lot but end up in a broken make buildworld. Any ideas waht I'm doing wrong? I sadly don't have any idea if the patch applies cleanly anymore to recent 8.STABLE - I did my testing on 8.1_PRERELEASE, where the patch applied cleanly. There was some talk about updating the patch when the problem was discussed more widely, but nothing has been realised this far. I might be able to test the patch against 8.STABLE on my home system sometime this week - as of myself I just did some testing and troubleshooting back when the problem was discussed, as for myself having working Kerberos is still non-issue. Of course if Kerberos functionality is critical for you, you could try removing Kerberos from base system using /etc.src.conf and then install either kerberos from ports and then linking sasl/cyrus against that. -Reko -- Martin Schweizer off...@pc-service.ch PC-Service M. Schweizer GmbH; Bannholzstrasse 6; CH-8608 Bubikon Tel. +41 55 243 30 00; Fax: +41 55 243 33 22 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: CYRUS IMAP cyradm core dump problem
Am Thu, Sep 23, 2010 at 03:05:30PM +0300 Reko Turja schrieb: I applied the patch as suggested by Reko, but it seemed to make no difference After the patch recompiling and linking at least SASL is needed after buildworld and inatallation of new world. removing libgssapiv2 libs however, solved my cyradm problem will this cause issues into the future for any other ports I may need ti install ? Unless you need kerberos authentication at some point, removing the libs is non-issue. I'm running in the same situation as you (see http://www.freebsd.org/cgi/getmsg.cgi?fetch=846230+852662+/usr/local/www/db/text/2010/freebsd-stable/20101003.freebsd-stable). I did tried a lot but end up in a broken make buildworld. Any ideas waht I'm doing wrong? I sadly don't have any idea if the patch applies cleanly anymore to recent 8.STABLE - I did my testing on 8.1_PRERELEASE, where the patch applied cleanly. There was some talk about updating the patch when the problem was discussed more widely, but nothing has been realised this far. I might be able to test the patch against 8.STABLE on my home system sometime this week - as of myself I just did some testing and troubleshooting back when the problem was discussed, as for myself having working Kerberos is still non-issue. Of course if Kerberos functionality is critical for you, you could try removing Kerberos from base system using /etc.src.conf and then install either kerberos from ports and then linking sasl/cyrus against that. -Reko ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: CYRUS IMAP cyradm core dump problem
Hello Reko Am Thu, Sep 23, 2010 at 03:05:30PM +0300 Reko Turja schrieb: I applied the patch as suggested by Reko, but it seemed to make no difference After the patch recompiling and linking at least SASL is needed after buildworld and inatallation of new world. removing libgssapiv2 libs however, solved my cyradm problem will this cause issues into the future for any other ports I may need ti install ? Unless you need kerberos authentication at some point, removing the libs is non-issue. I'm running in the same situation as you (see http://www.freebsd.org/cgi/getmsg.cgi?fetch=846230+852662+/usr/local/www/db/text/2010/freebsd-stable/20101003.freebsd-stable). I did tried a lot but end up in a broken make buildworld. Any ideas waht I'm doing wrong? Regards, -- Martin Schweizer off...@pc-service.ch PC-Service M. Schweizer GmbH; Bannholzstrasse 6; CH-8608 Bubikon Tel. +41 55 243 30 00; Fax: +41 55 243 33 22 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: CYRUS IMAP cyradm core dump problem
I applied the patch as suggested by Reko, but it seemed to make no difference After the patch recompiling and linking at least SASL is needed after buildworld and inatallation of new world. removing libgssapiv2 libs however, solved my cyradm problem will this cause issues into the future for any other ports I may need ti install ? Unless you need kerberos authentication at some point, removing the libs is non-issue. -Reko ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
CYRUS IMAP cyradm core dump problem
Hi guys, I have successfully used Cyrus IMAP in the past on versions 5.x, 6.x and 7.x but am having a problem with a fresh installed ver 8.0 server when running the cyradm command I upgraded to ver 8.1, performed a portupgrade and still get the same result as follows root# cyradm 192.168.134.171 Segmentation fault: 11 (core dumped) root# does anyone have any ideas as to what I should be looking at to fix this ? regards, Tim Kerr ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: CYRUS IMAP cyradm core dump problem
I upgraded to ver 8.1, performed a portupgrade and still get the same result as follows root# cyradm 192.168.134.171 The main question is - do you need kerberos/gssapi authentication on your server or not? If not, the easy fix is removing libgssapiv2 libs from /usr/local/lib/sasl2 For some reason, the gssapi implementation on FreeBSD 8+ is partial or broken and one way for more information and possible fix for gsspai see http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/147454 -Reko ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: CYRUS IMAP cyradm core dump problem
This happens for me if the password is entered incorrectly. I see it happens right away for you, but what if you type: cyradm -u username 192.168.134.171 ? Patrick On Wed, Sep 22, 2010 at 12:25 AM, Tim Kerr ti...@psst.com.au wrote: Hi guys, I have successfully used Cyrus IMAP in the past on versions 5.x, 6.x and 7.x but am having a problem with a fresh installed ver 8.0 server when running the cyradm command I upgraded to ver 8.1, performed a portupgrade and still get the same result as follows root# cyradm 192.168.134.171 Segmentation fault: 11 (core dumped) root# does anyone have any ideas as to what I should be looking at to fix this ? regards, Tim Kerr ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: CYRUS IMAP cyradm core dump problem
thanks everyone for all your help I applied the patch as suggested by Reko, but it seemed to make no difference removing libgssapiv2 libs however, solved my cyradm problem will this cause issues into the future for any other ports I may need ti install ? regards, Tim I upgraded to ver 8.1, performed a portupgrade and still get the same result as follows root# cyradm 192.168.134.171 The main question is - do you need kerberos/gssapi authentication on your server or not? If not, the easy fix is removing libgssapiv2 libs from /usr/local/lib/sasl2 For some reason, the gssapi implementation on FreeBSD 8+ is partial or broken and one way for more information and possible fix for gsspai see http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/147454 -Reko ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Core dump with php52-recode?
Hi! I just did a portsnap and found that php52 had been updated. When I recompiled (using `portmaster -i php52 php52-extensions`, suddenly php started crashing: Jun 9 10:27:30 hedwig kernel: pid 35517 (php), uid 1001: exited on signal 11 (core dumped) I was able to trace this down to the php52-recode extension. Has anyone else noticed this behaviour? Thanks, Ricky The information in this e-mail is intended only for the person to whom it is addressed. If you believe this e-mail was sent to you in error and the e-mail contains patient information, please contact the Partners Compliance HelpLine at http://www.partners.org/complianceline . If the e-mail was sent to you in error but does not contain patient information, please contact the sender and properly dispose of the e-mail. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Core dump with php52-recode?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Richard Morse wrote: Hi! I just did a portsnap and found that php52 had been updated. When I recompiled (using `portmaster -i php52 php52-extensions`, suddenly php started crashing: Jun 9 10:27:30 hedwig kernel: pid 35517 (php), uid 1001: exited on signal 11 (core dumped) I was able to trace this down to the php52-recode extension. Has anyone else noticed this behaviour? Thanks, Ricky Hi Ricky, I ran into a similar problem a while back and corrected it by re-ordering the PHP extensions.ini file. Perhaps these pages will help troubleshoot the problem: http://nerdstock.org/php_extensions?lang=en http://www.pingle.org/2007/09/22/php-crashes-extensions-workaround Hope that helps, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/sourcehosting/ - Follow me, follow you -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFMD7I00sRouByUApARArYvAJoCtyHnjjr16X9aJ801+HazpGucJgCffQPN tGah/ScE2ZIIcfylZnw2NGQ= =q4IX -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
python core dump during portupgrade firefox
Hi, I tried to portupgrade firefox from 3.6.2 to 3.6.3 (on FBSD 8.0-ST). It fails with: ... ../../../../other-licenses/ply/ply/yacc.py:74: DeprecationWarning: the md5 module is deprecated; use hashlib instead import re, types, sys, cStringIO, md5, os.path gmake[4]: *** [dom_quickstubs.cpp] Segmentation fault: 11 (core dumped) gmake[4]: *** Waiting for unfinished jobs xpccomponents.cpp: In function 'nsresult xpc_EvalInSandbox(JSContext*, JSObject*, const nsAString_internal, const char*, PRInt32, JSVersion, PRBool, jsval*)': xpccomponents.cpp:3602: warning: 'sus.AutoJSSuspendRequestWithNoCallContext::mDepth' may be used uninitialized in this function xpccomponents.cpp:3614: warning: 'sus.AutoJSSuspendRequestWithNoCallContext::mDepth' may be used uninitialized in this function gmake[4]: Leaving directory `/usr/ports/www/firefox/work/mozilla-1.9.2/js/src/xpconnect/src' gmake[3]: *** [libs] Error 2 gmake[3]: Leaving directory `/usr/ports/www/firefox/work/mozilla-1.9.2/js/src/xpconnect' gmake[2]: *** [libs_tier_gecko] Error 2 gmake[2]: Leaving directory `/usr/ports/www/firefox/work/mozilla-1.9.2' gmake[1]: *** [tier_gecko] Error 2 gmake[1]: Leaving directory `/usr/ports/www/firefox/work/mozilla-1.9.2' gmake: *** [default] Error 2 ... I got a coredump from python2.6 so I guess something is wrong with firefox or python or the combination of the two. Has this something to do with the portstree being a mess at this moment? Thanks, Marco -- Finding out what goes on in the C.I.A. is like performing acupuncture on a rock. -- New York Times, Jan. 20, 1981 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: python core dump during portupgrade firefox
On Sun, 18 Apr 2010, Marco Beishuizen wrote: Hi, I tried to portupgrade firefox from 3.6.2 to 3.6.3 (on FBSD 8.0-ST). It fails with: ... ../../../../other-licenses/ply/ply/yacc.py:74: DeprecationWarning: the md5 module is deprecated; use hashlib instead import re, types, sys, cStringIO, md5, os.path gmake[4]: *** [dom_quickstubs.cpp] Segmentation fault: 11 (core dumped) gmake[4]: *** Waiting for unfinished jobs xpccomponents.cpp: In function 'nsresult xpc_EvalInSandbox(JSContext*, JSObject*, const nsAString_internal, const char*, PRInt32, JSVersion, PRBool, jsval*)': xpccomponents.cpp:3602: warning: 'sus.AutoJSSuspendRequestWithNoCallContext::mDepth' may be used uninitialized in this function xpccomponents.cpp:3614: warning: 'sus.AutoJSSuspendRequestWithNoCallContext::mDepth' may be used uninitialized in this function gmake[4]: Leaving directory `/usr/ports/www/firefox/work/mozilla-1.9.2/js/src/xpconnect/src' gmake[3]: *** [libs] Error 2 gmake[3]: Leaving directory `/usr/ports/www/firefox/work/mozilla-1.9.2/js/src/xpconnect' gmake[2]: *** [libs_tier_gecko] Error 2 gmake[2]: Leaving directory `/usr/ports/www/firefox/work/mozilla-1.9.2' gmake[1]: *** [tier_gecko] Error 2 gmake[1]: Leaving directory `/usr/ports/www/firefox/work/mozilla-1.9.2' gmake: *** [default] Error 2 ... I got a coredump from python2.6 so I guess something is wrong with firefox or python or the combination of the two. Has this something to do with the portstree being a mess at this moment? It seems that something else did something to my python installation. I reinstalled python26 and the portupgrade succeeded. regards Marco -- I got my driver's license photo taken out of focus on purpose. Now when I get pulled over the cop looks at it (moving it nearer and farther, trying to see it clearly)... and says, Here, you can go. -- Steven Wright ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Help with core dump
Hi, I've installed from ports net-im/mu-conference, but whenever I try to start it I get a core dump. Running it through gdb I get the following: ]# gdb /usr/local/bin/mu-conference GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as amd64-marcel-freebsd...(no debugging symbols found)... (gdb) run -c /usr/local/etc/muc.xml Starting program: /usr/local/bin/mu-conference -c /usr/local/etc/muc.xml (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[New LWP 100228] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[New Thread 8015021c0 (LWP 100228)] Jabber Component Runtime -- 0.2.4 (c) 2003-2004 Paul Curtis Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 8015021c0 (LWP 100228)] 0x000800eaa386 in strlen () from /lib/libc.so.7 (gdb) # uname -a FreeBSD it05.ex.local 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:02:08 UTC 2009 r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 # cat /usr/local/etc/muc.xml jcr !-- This is a config file for a copy of MU-Conference, compiled against the Jabber Component Runtime (JCR). This is the same file that I use to connect to my development server, running jabberd2 beta2 In order to connect to a jabberd v1.4 server, simply change the name value to muclinker, and make sure the muclinker section is in your main jabber.xml file, as per the MU-Conference README file. -- nameconference.localhost/name !-- the jid of your component -- hostconference.localhost/host !-- this should be the same as above -- iplocalhost/ip !-- adress of the jabber server -- port7009/port !-- port used to connect the service to the jabber server -- secretVonyunya/secret !-- secret shared with the jabber server -- spool/var/spool/jabberd/conference.localhost/spool !-- directory containing the rooms data -- logdir/logdir !-- directory containing the debug log (the file is called mu-conference.log) -- pidfile/var/run/jabberd/mu-conference.pid/pidfile !-- file that will contain the PID of the process -- !-- logstderr/ -- !-- uncomment to also send log to stderr -- loglevel155/loglevel !-- log verbosity, 255 for very verbose, 0 for quiet -- conference xmlns=jabber:config:conference public/ !-- rooms are public when created, comment to make them private by default -- !-- the vCard section contains the vCard of the service -- vCard FNPublic Chatrooms/FN DESCThis service is for public chatrooms./DESC URLhttp://foo.bar//URL /vCard history40/history !-- maximum numbers of history lines send when joining a room -- logdir/var/spool/jabberd/conference.localhost/logs//logdir !-- where to store the room logs, comment to disable logging -- !--logsubdirs/-- !-- uncomment to stores the room logs in subdirs (for example 2007/08/02) -- stylesheet../style.css/stylesheet !--URL of the log stylesheet -- !-- default text to send to legacy clients, will also be used in the logs -- notice joinhas become available/join leavehas left/leave renameis now known as/rename /notice !-- lists of admins of the service, add a user/ tag by admin -- sadmin userad...@localhost/user /sadmin dynamic/ !-- persistent/ -- !-- persistent rooms will be created, overide dynamic/ -- !-- locknicks/ -- !-- enforce the user nickname to the user part of his jid -- !-- roomlock/ -- !-- uncomment to allow only admins to create rooms -- hideempty/ !-- configuration of MySQL, only used if the MySQL exports is activated, see README.sql -- !--mysql userroot/user pass/ databasechat/database hostlocalhost/host /mysql-- /conference /jcr Any idea what can be wrong? Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Help with core dump
El 20/01/10 10:18, Matias escribió: Hi, I've installed from ports net-im/mu-conference, but whenever I try to start it I get a core dump. Running it through gdb I get the following: ]# gdb /usr/local/bin/mu-conference GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as amd64-marcel-freebsd...(no debugging symbols found)... (gdb) run -c /usr/local/etc/muc.xml Starting program: /usr/local/bin/mu-conference -c /usr/local/etc/muc.xml (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[New LWP 100228] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[New Thread 8015021c0 (LWP 100228)] Jabber Component Runtime -- 0.2.4 (c) 2003-2004 Paul Curtis Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 8015021c0 (LWP 100228)] 0x000800eaa386 in strlen () from /lib/libc.so.7 (gdb) # uname -a FreeBSD it05.ex.local 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:02:08 UTC 2009 r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 # cat /usr/local/etc/muc.xml jcr !-- This is a config file for a copy of MU-Conference, compiled against the Jabber Component Runtime (JCR). This is the same file that I use to connect to my development server, running jabberd2 beta2 In order to connect to a jabberd v1.4 server, simply change the name value to muclinker, and make sure the muclinker section is in your main jabber.xml file, as per the MU-Conference README file. -- nameconference.localhost/name !-- the jid of your component -- hostconference.localhost/host !-- this should be the same as above -- iplocalhost/ip !-- adress of the jabber server -- port7009/port !-- port used to connect the service to the jabber server -- secretVonyunya/secret !-- secret shared with the jabber server -- spool/var/spool/jabberd/conference.localhost/spool !-- directory containing the rooms data -- logdir/logdir !-- directory containing the debug log (the file is called mu-conference.log) -- pidfile/var/run/jabberd/mu-conference.pid/pidfile !-- file that will contain the PID of the process -- !-- logstderr/ -- !-- uncomment to also send log to stderr -- loglevel155/loglevel !-- log verbosity, 255 for very verbose, 0 for quiet -- conference xmlns=jabber:config:conference public/ !-- rooms are public when created, comment to make them private by default -- !-- the vCard section contains the vCard of the service -- vCard FNPublic Chatrooms/FN DESCThis service is for public chatrooms./DESC URLhttp://foo.bar//URL /vCard history40/history !-- maximum numbers of history lines send when joining a room -- logdir/var/spool/jabberd/conference.localhost/logs//logdir !-- where to store the room logs, comment to disable logging -- !--logsubdirs/-- !-- uncomment to stores the room logs in subdirs (for example 2007/08/02) -- stylesheet../style.css/stylesheet !--URL of the log stylesheet -- !-- default text to send to legacy clients, will also be used in the logs -- notice joinhas become available/join leavehas left/leave renameis now known as/rename /notice !-- lists of admins of the service, add a user/ tag by admin -- sadmin userad...@localhost/user /sadmin dynamic/ !-- persistent/ -- !-- persistent rooms will be created, overide dynamic/ -- !-- locknicks/ -- !-- enforce the user nickname to the user part of his jid -- !-- roomlock/ -- !-- uncomment to allow only admins to create rooms -- hideempty/ !-- configuration of MySQL, only used if the MySQL exports is activated, see README.sql -- !--mysql userroot/user pass/ databasechat/database hostlocalhost/host /mysql-- /conference /jcr Any idea what can be wrong? Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org I've finally solved it by enabling linux compatibility kernel module. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Trouble getting a core dump from clamd
On Tue, January 19, 2010 12:35, Chuck Swiger wrote: Hi-- On Jan 19, 2010, at 10:04 AM, Doug Poland wrote: No joy. # sysctl kern.corefile=/var/crash/clamd.core # /usr/local/etc/rc.d/clamav-clamd start Starting clamav_clamd. Segmentation fault # ll /var/crash total 2 -rw-r--r-- 1 root wheel 5 Apr 10 2005 minfree Please see man 5 core; in particular, clamd changes userid: By default, a process that changes user or group credentials whether real or effective will not create a corefile. This behaviour can be changed to generate a core dump by setting the sysctl(8) variable kern.sugid_coredump to 1. ...so you will need to toggle that sysctl also. I'd suggest doing something more like: mkdir /cores chmod 1777 /cores sysctl kern.sugid_coredump=1 sysctl kern.corefile=/cores/%N.%P.core ...but adjust the path to be under /var or /usr if free diskspace makes doing so necessary. Thanks for the suggestion and the pointer to man 5 core. I implemented your suggestions but still get no core dump. Very strange... -- Regards, Doug ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Trouble getting a core dump from clamd
Hi--
On Jan 20, 2010, at 12:46 PM, Doug Poland wrote:
Thanks for the suggestion and the pointer to man 5 core. I
implemented your suggestions but still get no core dump. Very
strange...
Check your default resource limits (shell startup files /etc/login.conf) and
see whether coredumpsize is set to 0, maybe? If you build and run:
% cat crash.c
#include stdlib.h
main()
{
char *bad = NULL;
bad[0] = '1';
}
% cc -o crash crash.c
% ./crash
[1]16550 segmentation fault (core dumped) ./crash
% ls /cores
crash.16550.core
...do you get this trivial program to dump core?
Regards,
--
-Chuck
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Trouble getting a core dump from clamd
On Wed, January 20, 2010 15:05, Chuck Swiger wrote:
Hi--
On Jan 20, 2010, at 12:46 PM, Doug Poland wrote:
Thanks for the suggestion and the pointer to man 5 core. I
implemented your suggestions but still get no core dump. Very
strange...
Check your default resource limits (shell startup files
/etc/login.conf) and see whether coredumpsize is set to 0, maybe?
Nope, nothin'
% set | grep core | egrep -v grep
% env | grep core | egrep -v grep
% grep core /etc/login.c* | egrep -v #
/etc/login.conf::coredumpsize=unlimited:\
If you build and run:
% cat crash.c
#include stdlib.h
main()
{
char *bad = NULL;
bad[0] = '1';
}
% cc -o crash crash.c
% ./crash
[1]16550 segmentation fault (core dumped) ./crash
% ls /cores
crash.16550.core
...do you get this trivial program to dump core?
No, not on the system in question. Just tried it on a plain-vanilla
8.0-RELEASE box I just built and I do get the the core dump there.
% echo $SHELL
/bin/tcsh
% uname -a
FreeBSD hostname.domain.com 7.2-RELEASE-p3 FreeBSD 7.2-RELEASE-p3 #0:
Sat Sep 12 11:15:05 CDT 2009
r...@hostname.domain.com:/usr/obj/usr/src/sys/GENERIC-SERVER i386
% cat /sys/i386/conf/GENERIC-SERVER
ident GENERIC-SERVER
include GENERIC
options INCLUDE_CONFIG_FILE # Include this file in kernel
options QUOTA
% sysctl -a | grep core
kern.corefile: /var/coredumps/%U/%N.core
kern.nodump_coredump: 0
kern.coredump: 1
kern.sugid_coredump: 1
debug.elf32_legacy_coredump: 1
% touch /var/coredumps/file
% ll !$
ll /var/coredumps/file
-rw-r--r-- 1 doug wheel 0 Jan 20 15:13 /var/coredumps/file
--
Regards,
Doug
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Trouble getting a core dump from clamd
Hi-- On Jan 20, 2010, at 1:24 PM, Doug Poland wrote: % sysctl -a | grep core kern.corefile: /var/coredumps/%U/%N.core Does /var/coredumps/doug and/or /var/coredumps/clamav exist and have appropriate permissions (or be 1777 like /tmp to avoid a problem with that)...? -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Trouble getting a core dump from clamd
On Wed, 20 Jan 2010 15:24:51 -0600 Doug Poland wrote: % sysctl -a | grep core kern.corefile: /var/coredumps/%U/%N.core As CORE(5) says %U is a UID... % touch /var/coredumps/file % ll !$ ll /var/coredumps/file -rw-r--r-- 1 doug wheel 0 Jan 20 15:13 /var/coredumps/file ... so you should have a directory /var/coredumps/UID owned by (well, at least have permissions to write by) this UID. -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Trouble getting a core dump from clamd
On 2010-01-20 17:11, Boris Samorodov wrote: On Wed, 20 Jan 2010 15:24:51 -0600 Doug Poland wrote: % sysctl -a | grep core kern.corefile: /var/coredumps/%U/%N.core As CORE(5) says %U is a UID... % touch /var/coredumps/file % ll !$ ll /var/coredumps/file -rw-r--r-- 1 doug wheel 0 Jan 20 15:13 /var/coredumps/file ... so you should have a directory /var/coredumps/UID owned by (well, at least have permissions to write by) this UID. That was it, thanks for the keen vision! -- Regards, Doug ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Trouble getting a core dump from clamd
Hello, I'm running 7.2-RELEASE-p3 i386 and am having an issue getting a core dump from a program that is seg faulting. Last night, inexplicably, clamd started to seg fault. I was trying to obtain a core dump for further analysis but no .core file can be found. I've tried the following in a tcsh: # sysctl -a | grep core kern.corefile: %N.core kern.nodump_coredump: 0 kern.coredump: 1 kern.sugid_coredump: 0 debug.elf32_legacy_coredump: 0 # set ulimit=-c # /usr/local/sbin/clamd /usr/local/etc/clamd.conf Segmentation fault # tail /var/log/messages Jan 19 10:16:19 hostname kernel: pid 42315 (clamd), uid 106: exited on signal 11 But I get no .core file. Suggestions? -- Regards, Doug ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Trouble getting a core dump from clamd
2010/1/19 Doug Poland d...@polands.org Hello, I'm running 7.2-RELEASE-p3 i386 and am having an issue getting a core dump from a program that is seg faulting. Last night, inexplicably, clamd started to seg fault. I was trying to obtain a core dump for further analysis but no .core file can be found. I've tried the following in a tcsh: # sysctl -a | grep core kern.corefile: %N.core kern.nodump_coredump: 0 kern.coredump: 1 kern.sugid_coredump: 0 debug.elf32_legacy_coredump: 0 # set ulimit=-c # /usr/local/sbin/clamd /usr/local/etc/clamd.conf Segmentation fault # tail /var/log/messages Jan 19 10:16:19 hostname kernel: pid 42315 (clamd), uid 106: exited on signal 11 But I get no .core file. Suggestions? -- Regards, Doug ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org set a path in the sysctl variable kern.corefile. WIll make the core file easier to find if one is generated. Generally much tider as well then having core files littered all over the system ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Trouble getting a core dump from clamd
On Tue, January 19, 2010 11:10, krad wrote: 2010/1/19 Doug Poland d...@polands.org Hello, I'm running 7.2-RELEASE-p3 i386 and am having an issue getting a core dump from a program that is seg faulting. set a path in the sysctl variable kern.corefile. WIll make the core file easier to find if one is generated. Generally much tider as well then having core files littered all over the system No joy. # sysctl kern.corefile=/var/crash/clamd.core # /usr/local/etc/rc.d/clamav-clamd start Starting clamav_clamd. Segmentation fault # ll /var/crash total 2 -rw-r--r-- 1 root wheel 5 Apr 10 2005 minfree -- Regards, Doug ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Trouble getting a core dump from clamd
Hi-- On Jan 19, 2010, at 10:04 AM, Doug Poland wrote: No joy. # sysctl kern.corefile=/var/crash/clamd.core # /usr/local/etc/rc.d/clamav-clamd start Starting clamav_clamd. Segmentation fault # ll /var/crash total 2 -rw-r--r-- 1 root wheel 5 Apr 10 2005 minfree Please see man 5 core; in particular, clamd changes userid: By default, a process that changes user or group credentials whether real or effective will not create a corefile. This behaviour can be changed to generate a core dump by setting the sysctl(8) variable kern.sugid_coredump to 1. ...so you will need to toggle that sysctl also. I'd suggest doing something more like: mkdir /cores chmod 1777 /cores sysctl kern.sugid_coredump=1 sysctl kern.corefile=/cores/%N.%P.core ...but adjust the path to be under /var or /usr if free diskspace makes doing so necessary. Regards, -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
MimeDefang: Perl core dump
Hello My goal is to add to all outgoing mail a small boilerplate. My system: FreeBSD acsvfbsd06.acutronic.ch 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Thu Sep 17 17:53:59 CEST 2009 mar...@acsvfbsd06.acutronic.ch:/usr/obj/usr/src/sys/GENERIC amd64 sendmail.mc: [snip] MAIL_FILTER(`mimedefang', `S=local:/var/spool/MIMEDefang/mimedefang.sock, F=T, T=S:1m;R:1m')dnl define(`confINPUT_MAIL_FILTERS', `mimedefang')dnl [snip] sendmail version: ESMTP Sendmail 8.14.3/8.14.3; Fri, 27 Nov 2009 17:58:56 +0100 (CET) acsvfbsd06# mimedefang.pl -test Filter /usr/local/etc/mimedefang/mimedefang-filter seems syntactically correct. acsvfbsd06# mimedefang.pl -features MIMEDefang version 2.67 Archive::Zip : yes HTML::Parser : yes Net::DNS : yes Path:CONFDIR : yes (/usr/local/etc/mimedefang) Path:QUARANTINEDIR: yes (/var/spool/MD-Quarantine) Path:SENDMAIL : yes (/usr/sbin/sendmail) Path:SPOOLDIR : yes (/var/spool/MIMEDefang) SpamAssassin : yes HTML:TokeParser : no HTMLCleaner : no Unix::Syslog : no Virus:AVP : no Virus:AVP5: no Virus:BDC : no Virus:CLAMAV : no Virus:CLAMD : no Virus:CSAV: no Virus:FPROT : no Virus:FPROTD : no Virus:FPROTD6 : no Virus:FPSCAN : no Virus:FSAV: no Virus:HBEDV : no Virus:KAVSCANNER : no Virus:NAI : no Virus:NOD32 : no Virus:NVCC: no Virus:SAVSCAN : no Virus:SOPHIE : no Virus:SOPHOS : no Virus:SymantecCSS : no Virus:TREND : no Virus:TROPHIE : no Virus:VEXIRA : no Anomy::HTMLCleaner: missing Archive::Zip : Version 1.30 Digest::SHA1 : Version 2.12 HTML::Parser : Version 3.64 HTML::TokeParser : missing IO::Socket: Version 1.31 IO::Stringy : Version 2.110 MIME::Base64 : Version 3.08 MIME::Tools : Version 5.427 MIME::Words : Version 5.427 Mail::Mailer : Version 2.04 Mail::SpamAssassin: Version 3.002005 Net::DNS : Version 0.65 Unix::Syslog : Version 1.1 ps -ax shows 6722 ?? S 0:00,19 /usr/local/bin/mimedefang-multiplexor -l -p /var/spool/MIMEDefang/mimedefang-multiplexor.pid -z /var/spool/MIMEDefang -m 2 -x 10 -U The -l option means to log all stuff to syslog. /var/log/all.log shows: Nov 27 17:57:18 acsvfbsd06 kernel: pid 9919 (perl), uid 26: exited on signal 11 (core dumped) Nov 27 17:57:18 acsvfbsd06 mimedefang-multiplexor[6722]: Reap: slave 0 (pid 9919) exited due to signal 11 (SLAVE DIED UNEXPECTEDLY) Nov 27 17:57:18 acsvfbsd06 mimedefang-multiplexor[6722]: Slave 0 resource usage: req=0, scans=0, user=0.158, sys=0.067, nswap=0, majflt=0, minflt=2832, maxrss The above will repeate any 30 seconds. I also ant find the core files but I could not find it! (Or I did not find the correct directory) Any ideas what is going wrong here? -- Martin Schweizer off...@pc-service.ch PC-Service M. Schweizer GmbH; Bannholzstrasse 6; CH-8608 Bubikon Tel. +41 55 243 30 00; Fax: +41 55 243 33 22; http://www.pc-service.ch; public key : http://www.pc-service.ch/pgp/public_key.asc; fingerprint: EC21 CA4D 5C78 BC2D 73B7 10F9 C1AE 1691 D30F D239; ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: system() call causes core dump
On Saturday 31 October 2009 21:52:37 Peter Steele wrote:
In UNIX it is not safe to perform arbitrary actions after forking a
multi-threaded process. You're basically expected to call exec soon
after the fork, although you can do certain other work if you are very
careful.
The reason for this is that after the fork, only one thread will be
running in the child, and if that thread tries to acquire a lock or other
formerly-shared resource it may deadlock or crash, because the child
process is no longer accessing the same memory location as the threads in
the parent process (it gets a separate copy of the address space at the
time of fork, which may not be in a consistent state from the point of
view of the thread library).
I am not calling fork explicitly. The thread I'm running in was created
with pthread_create(). The fork() in the stack trace in my original email
is being called by the system() function as it spawns off the process it
is supposed want to run. Is there a safe way to call system() within a
pthread?
Either I'm very lucky, or popen is better suited for this, as I have this
running on various machines, 24/7:
#define PING_CMD \
ping -n -c 50 %s 2/dev/null|egrep 'round-trip|packets received'
/* worker thread main loop */
void *monitor_host(void *data)
{
...
if( -1 == asprintf(cmd, PING_CMD, ip) )
{
warnl(Failed to construct command);
*ex = EX_OSERR;
return(ex);
}
while( !signalled )
{
if( (cmd_p = popen(cmd, r)) == NULL )
{
warnl(Failed to run command %s, cmd);
*ex = EX_OSERR;
return(ex);
}
EV_SET(ch, fileno(cmd_p), EVFILT_READ, EV_ADD|EV_ENABLE,
0, 0, NULL);
for( ;; )
{
int nev;
if( signalled ||
(nev = kevent(kq, ch, 1, ev, 1, timeout)) == -1 )
{
if( signalled == SIGHUP )
goto closeproc;
else
goto cleanup;
}
if( nev )
break;
}
/* read fp, store in db */
}
}
--
Mel
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: system() call causes core dump
On Sat, Oct 31, 2009 at 4:55 PM, Kris Kennaway k...@freebsd.org wrote: Peter Steele wrote: I have an application running a number of threads. I've had recent instances where the code below is causing a core dump to occur: char fstatCmd[200]; char *fstatOut = /tmp/fstat.out; sprintf(fstatCmd, fstat | grep -v USER | wc -l %s, fstatOut); rc = system(fstatCmd); The call is simply intended to get a count of the current open handles. The system call though causes a core: #0 0x000801058307 in _spinunlock () from /lib/libthr.so.3 #1 0x0008011d0afb in _malloc_postfork () from /lib/libc.so.7 #2 0x00080105c5fb in fork () from /lib/libthr.so.3 #3 0x000801191aae in system () from /lib/libc.so.7 #4 0x0008010553aa in system () from /lib/libthr.so.3 #5 0x0040b6f9 in mythread at myapp.c:461 #6 0x000801056a88 in pthread_getprio () from /lib/libthr.so.3 There appears to be some kind of thread-safe issue going on. I have a number of threads that are monitoring various items, waking up a differing intervals to do their respective tasks. Do I need to put in a global mutex so that the threads never attempt to make simultaneous system() calls? Curiously, only this particular system() call appears to be causing a core. In UNIX it is not safe to perform arbitrary actions after forking a multi-threaded process. You're basically expected to call exec soon after the fork, although you can do certain other work if you are very careful. The reason for this is that after the fork, only one thread will be running in the child, and if that thread tries to acquire a lock or other formerly-shared resource it may deadlock or crash, because the child process is no longer accessing the same memory location as the threads in the parent process (it gets a separate copy of the address space at the time of fork, which may not be in a consistent state from the point of view of the thread library). Are you saying system/popen can't be used in threads? Is there a workaround? ( forking manual and executing exec? ) Would calling 'system(exec fstat | ... result.txt)' make any difference? just curious, kind regards, usleep ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
system() call causes core dump
I have an application running a number of threads. I've had recent instances where the code below is causing a core dump to occur: char fstatCmd[200]; char *fstatOut = /tmp/fstat.out; sprintf(fstatCmd, fstat | grep -v USER | wc -l %s, fstatOut); rc = system(fstatCmd); The call is simply intended to get a count of the current open handles. The system call though causes a core: #0 0x000801058307 in _spinunlock () from /lib/libthr.so.3 #1 0x0008011d0afb in _malloc_postfork () from /lib/libc.so.7 #2 0x00080105c5fb in fork () from /lib/libthr.so.3 #3 0x000801191aae in system () from /lib/libc.so.7 #4 0x0008010553aa in system () from /lib/libthr.so.3 #5 0x0040b6f9 in mythread at myapp.c:461 #6 0x000801056a88 in pthread_getprio () from /lib/libthr.so.3 There appears to be some kind of thread-safe issue going on. I have a number of threads that are monitoring various items, waking up a differing intervals to do their respective tasks. Do I need to put in a global mutex so that the threads never attempt to make simultaneous system() calls? Curiously, only this particular system() call appears to be causing a core. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: system() call causes core dump
Peter Steele wrote: I have an application running a number of threads. I've had recent instances where the code below is causing a core dump to occur: char fstatCmd[200]; char *fstatOut = /tmp/fstat.out; sprintf(fstatCmd, fstat | grep -v USER | wc -l %s, fstatOut); rc = system(fstatCmd); The call is simply intended to get a count of the current open handles. The system call though causes a core: #0 0x000801058307 in _spinunlock () from /lib/libthr.so.3 #1 0x0008011d0afb in _malloc_postfork () from /lib/libc.so.7 #2 0x00080105c5fb in fork () from /lib/libthr.so.3 #3 0x000801191aae in system () from /lib/libc.so.7 #4 0x0008010553aa in system () from /lib/libthr.so.3 #5 0x0040b6f9 in mythread at myapp.c:461 #6 0x000801056a88 in pthread_getprio () from /lib/libthr.so.3 There appears to be some kind of thread-safe issue going on. I have a number of threads that are monitoring various items, waking up a differing intervals to do their respective tasks. Do I need to put in a global mutex so that the threads never attempt to make simultaneous system() calls? Curiously, only this particular system() call appears to be causing a core. In UNIX it is not safe to perform arbitrary actions after forking a multi-threaded process. You're basically expected to call exec soon after the fork, although you can do certain other work if you are very careful. The reason for this is that after the fork, only one thread will be running in the child, and if that thread tries to acquire a lock or other formerly-shared resource it may deadlock or crash, because the child process is no longer accessing the same memory location as the threads in the parent process (it gets a separate copy of the address space at the time of fork, which may not be in a consistent state from the point of view of the thread library). Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: system() call causes core dump
In UNIX it is not safe to perform arbitrary actions after forking a multi-threaded process. You're basically expected to call exec soon after the fork, although you can do certain other work if you are very careful. The reason for this is that after the fork, only one thread will be running in the child, and if that thread tries to acquire a lock or other formerly-shared resource it may deadlock or crash, because the child process is no longer accessing the same memory location as the threads in the parent process (it gets a separate copy of the address space at the time of fork, which may not be in a consistent state from the point of view of the thread library). I am not calling fork explicitly. The thread I'm running in was created with pthread_create(). The fork() in the stack trace in my original email is being called by the system() function as it spawns off the process it is supposed want to run. Is there a safe way to call system() within a pthread? The app has several such threads doing various monitoring actions, some calling functions using system(), others invoking various C library routines. The parent process where these threads were spawned from is basically sleeping, waking up only periodically to check for shutdown events. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
STOP state in top + segmentation fault and core dump?
Hi, When I run many heavily multi-threaded (1000+ threads/process) and memory intensive (1800 MB+/process) processes on FreeBSD 8.0 amd64, some of them get in STOP state in top and then seg fault and core dump. Are stop states in top caused by seg faults or it is the OS that stops the processes because they exceed some limit? I do not see any message about any limit being exceeded. The machine has 12GB of memory so it should be able to sustain 4 processes using 1800MB each of memory I guess (I have 12 GB of swap space anyway but it stays unused). Everything runs fine if I run a single process and I have never encountered such problems when running these on Linux. Anyone has an idea? I am using the default limits right now: limit cputime unlimited filesize unlimited datasize 33554432 kbytes stacksize524288 kbytes coredumpsize unlimited memoryuseunlimited vmemoryuse unlimited descriptors 11095 memorylocked unlimited maxproc 5547 sbsize unlimited swapsize unlimited Thank you! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Apache20 port on FreeBSD 7.2 does a core dump
On Sat, 3 Oct 2009 13:38 -, aaflatooni wrote: Aflatoon Aflatooni writes: I am getting a lot of core dumps and Apache20 freezing. I have installed the porting using the following make: make WITHOUT_MODULES=ssl status speling imap auth_dbm auth_digest dav dav_fs cern_meta cgi include install any suggestions as to how I might find out what is causing the problem and the core dumps. The first thing I'd try is re-including the excluded modules. If you no longer get the crashes, you can start narrowing in on which one is involved. If you still get the crashes, you'll have to start looking at the core files. I'm assuming you're not used to using a debugger on a core file, on the theory that you would have done that already if you were comfortable with it. I originally had them included and I was getting the core dumps, but I removed them because I don't need them and I am still getting the core dumps. This is a production box and it would be hard to have debugger turned on. I don't know if it would be helpful, but PHP is also really slow on this machine. I know that PHP would cause a dump in the php.core file and not apache.core. How do I inspect the core file to find out which module caused it? Thanks Have you any special php5 modules loaded. I had a problem with I want to recall three or more extensions that would cause apache2X to dump core or halt in doing any further actions upon request. If the above is the case you can disable some or all of your php5-extensions in local/etc/php/extensions.ini to test it out. Best of luck. Thanks, I followed your suggestion and removed all but the necessary modules from the extensions.ini. I will have to wait and see if it helps the core dumps. So at this time I have the following in the extensions: extension=gd.so extension=mcrypt.so extension=mysql.so extension=simplexml.so extension=spl.so extension=mysqli.so extension=session.so extension=tokenizer.so extension=xml.so PHP is still slow though! Just an update: I still get the httpd.core dumps and PHP5 is visibly slower. Nothing has helped the situation. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Apache20 port on FreeBSD 7.2 does a core dump
Hi, I am getting a lot of core dumps and Apache20 freezing. I have installed the porting using the following make: make WITHOUT_MODULES=ssl status speling imap auth_dbm auth_digest dav dav_fs cern_meta cgi include install any suggestions as to how I might find out what is causing the problem and the core dumps. Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Apache20 port on FreeBSD 7.2 does a core dump
Aflatoon Aflatooni aaflato...@yahoo.com writes: I am getting a lot of core dumps and Apache20 freezing. I have installed the porting using the following make: make WITHOUT_MODULES=ssl status speling imap auth_dbm auth_digest dav dav_fs cern_meta cgi include install any suggestions as to how I might find out what is causing the problem and the core dumps. The first thing I'd try is re-including the excluded modules. If you no longer get the crashes, you can start narrowing in on which one is involved. If you still get the crashes, you'll have to start looking at the core files. I'm assuming you're not used to using a debugger on a core file, on the theory that you would have done that already if you were comfortable with it. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Apache20 port on FreeBSD 7.2 does a core dump
Aflatoon Aflatooni writes: I am getting a lot of core dumps and Apache20 freezing. I have installed the porting using the following make: make WITHOUT_MODULES=ssl status speling imap auth_dbm auth_digest dav dav_fs cern_meta cgi include install any suggestions as to how I might find out what is causing the problem and the core dumps. The first thing I'd try is re-including the excluded modules. If you no longer get the crashes, you can start narrowing in on which one is involved. If you still get the crashes, you'll have to start looking at the core files. I'm assuming you're not used to using a debugger on a core file, on the theory that you would have done that already if you were comfortable with it. I originally had them included and I was getting the core dumps, but I removed them because I don't need them and I am still getting the core dumps. This is a production box and it would be hard to have debugger turned on. I don't know if it would be helpful, but PHP is also really slow on this machine. I know that PHP would cause a dump in the php.core file and not apache.core. How do I inspect the core file to find out which module caused it? Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Apache20 port on FreeBSD 7.2 does a core dump
On Sat, 3 Oct 2009 13:38 -, aaflatooni wrote:
Aflatoon Aflatooni writes:
I am getting a lot of core dumps and Apache20 freezing.
I have installed the porting using the following make:
make WITHOUT_MODULES=ssl status speling imap auth_dbm auth_digest dav dav_fs
cern_meta cgi include install
any suggestions as to how I might find out what is causing the problem and the
core dumps.
The first thing I'd try is re-including the excluded modules.
If you no longer get the crashes, you can start narrowing in on which
one is involved. If you still get the crashes, you'll have to start
looking at the core files.
I'm assuming you're not used to using a debugger on a core file,
on the theory that you would have done that already if you were
comfortable with it.
I originally had them included and I was getting the core dumps, but I removed
them because I don't need them and I am still getting the core dumps.
This is a production box and it would be hard to have debugger turned on.
I don't know if it would be helpful, but PHP is also really slow on this
machine. I know that PHP would cause a dump in the php.core file and not
apache.core.
How do I inspect the core file to find out which module caused it?
Thanks
Have you any special php5 modules loaded. I had a problem with I want to recall
three or more extensions that would cause apache2X to dump core or halt in doing
any further actions upon request.
If the above is the case you can disable some or all of your php5-extensions in
local/etc/php/extensions.ini to test it out.
Best of luck.
--
%{+
| dataix.net!jhell 2048R/89D8547E 2009-09-30 |
| BSD since FreeBSD 4.2Linux since Slackware 2.1 |
| 85EF E26B 07BB 3777 76BE B12A 9057 8789 89D8 547E |
+%}
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Apache20 port on FreeBSD 7.2 does a core dump
On Sat, 3 Oct 2009 13:38 -, aaflatooni wrote: Aflatoon Aflatooni writes: I am getting a lot of core dumps and Apache20 freezing. I have installed the porting using the following make: make WITHOUT_MODULES=ssl status speling imap auth_dbm auth_digest dav dav_fs cern_meta cgi include install any suggestions as to how I might find out what is causing the problem and the core dumps. The first thing I'd try is re-including the excluded modules. If you no longer get the crashes, you can start narrowing in on which one is involved. If you still get the crashes, you'll have to start looking at the core files. I'm assuming you're not used to using a debugger on a core file, on the theory that you would have done that already if you were comfortable with it. I originally had them included and I was getting the core dumps, but I removed them because I don't need them and I am still getting the core dumps. This is a production box and it would be hard to have debugger turned on. I don't know if it would be helpful, but PHP is also really slow on this machine. I know that PHP would cause a dump in the php.core file and not apache.core. How do I inspect the core file to find out which module caused it? Thanks Have you any special php5 modules loaded. I had a problem with I want to recall three or more extensions that would cause apache2X to dump core or halt in doing any further actions upon request. If the above is the case you can disable some or all of your php5-extensions in local/etc/php/extensions.ini to test it out. Best of luck. Thanks, I followed your suggestion and removed all but the necessary modules from the extensions.ini. I will have to wait and see if it helps the core dumps. So at this time I have the following in the extensions: extension=gd.so extension=mcrypt.so extension=mysql.so extension=simplexml.so extension=spl.so extension=mysqli.so extension=session.so extension=tokenizer.so extension=xml.so PHP is still slow though! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8.0 and GPT_PART and core-dump
On 7/16/09, Patrick Lamaiziere patf...@davenulle.org wrote: Hello, With 8.0, FreeBSD see my disk with several parts instead slices. That works fine but the kernel is not able to core dump to my swap (ad4p3a) and I can't break into the debuger (laptop with an usb keyboard). For first one it looks like table is broken. The last one is unrelated to gpart So I would like to revert to slices like with FreeBSD 7.2? Thanks, regards. baby-jane:~$ gpart show = 34 312581741 ad4 GPT (149G) 34 6 - free - (3.0K) 40 4096001 efi (200M) 409640 2262302722 !48465300--11aa-aa11-00306543ecac (108G) 226639912 262144 - free - (128M) 226902056 856797123 !ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 (41G) 312581768 7 - free - (3.5K) = 0 85679712 ad4p3 BSD (41G) 0 4194304 2 freebsd-swap (2.0G) 4194304 1572864 1 freebsd-ufs (768M) 5767168 2097152 4 freebsd-ufs (1.0G) 7864320 2097152 5 freebsd-ufs (1.0G) 9961472 75718240 6 freebsd-ufs (36G) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- Paul ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8.0 and GPT_PART and core-dump
Le Fri, 17 Jul 2009 09:30:25 +0200, Paul B. Mahol one...@gmail.com a écrit : With 8.0, FreeBSD see my disk with several parts instead slices. That works fine but the kernel is not able to core dump to my swap (ad4p3a) and I can't break into the debuger (laptop with an usb keyboard). For first one it looks like table is broken. It's a Macbook Pro partitionned with the Apple bootcamp utility. I'm not sure if I shall fill a PR for this, it looks to be a hack just for running MS-Windows on a Mac. But that worked fine with 7.X The last one is unrelated to gpart I know, I meant I really need to be able to dump a panic. Any hint is welcome. Regards. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8.0 and GPT_PART and core-dump
Patrick Lamaiziere wrote: Le Fri, 17 Jul 2009 09:30:25 +0200, Paul B. Mahol one...@gmail.com a écrit : With 8.0, FreeBSD see my disk with several parts instead slices. That works fine but the kernel is not able to core dump to my swap (ad4p3a) and I can't break into the debuger (laptop with an usb keyboard). For first one it looks like table is broken. It's a Macbook Pro partitionned with the Apple bootcamp utility. I'm not sure if I shall fill a PR for this, it looks to be a hack just for running MS-Windows on a Mac. But that worked fine with 7.X The last one is unrelated to gpart I know, I meant I really need to be able to dump a panic. Any hint is welcome. When the kernel attempts a dump on the device, do you perhaps see a message like partition type unsupported?. One thing that's changed in GPART is that it will not allow dumps on partitions marked like they contain a file system. Specifically, if you're using GPT, the dump partition's type needs to be either gpt_uuid_freebsd_swap or gpt_uuid_linux_swap. For FreeBSD swap, it's 516e7cb5‐6ecf‐11d6‐8ff8‐00022d09712b. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8.0 and GPT_PART and core-dump
Le Fri, 17 Jul 2009 12:27:32 +0200, Ivan Voras ivo...@freebsd.org a écrit : When the kernel attempts a dump on the device, do you perhaps see a message like partition type unsupported?. Yes at boot-time : GEOM_PART: Partition 'ad4p3' not suitable for kernel dumps (wrong type?) One thing that's changed in GPART is that it will not allow dumps on partitions marked like they contain a file system. Specifically, if you're using GPT, the dump partition's type needs to be either gpt_uuid_freebsd_swap or gpt_uuid_linux_swap. For FreeBSD swap, it's 516e7cb5‐6ecf‐11d6‐8ff8‐00022d09712b. I do not have a GPT partition for the swap. My swap is in ad4p3b = 0 85679712 ad4p3 BSD (41G) 0 4194304 2 freebsd-swap (2.0G) Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
8.0 and GPT_PART and core-dump
Hello, With 8.0, FreeBSD see my disk with several parts instead slices. That works fine but the kernel is not able to core dump to my swap (ad4p3a) and I can't break into the debuger (laptop with an usb keyboard). So I would like to revert to slices like with FreeBSD 7.2? Thanks, regards. baby-jane:~$ gpart show = 34 312581741 ad4 GPT (149G) 34 6 - free - (3.0K) 40 4096001 efi (200M) 409640 2262302722 !48465300--11aa-aa11-00306543ecac (108G) 226639912 262144 - free - (128M) 226902056 856797123 !ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 (41G) 312581768 7 - free - (3.5K) = 0 85679712 ad4p3 BSD (41G) 0 4194304 2 freebsd-swap (2.0G) 4194304 1572864 1 freebsd-ufs (768M) 5767168 2097152 4 freebsd-ufs (1.0G) 7864320 2097152 5 freebsd-ufs (1.0G) 9961472 75718240 6 freebsd-ufs (36G) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: pkg_delete core dump
Hi Mel, the link to download the +CONTENTS file is here http://www.megaupload.com/?d=YDKFRCZG, and you know what? I don't have +REQUIRED_BY file. thanks!! there is a empty entry in the +CONTENTS file: [snip] @pkgdep linux-scim-libs-1.4.4 @comment DEPORIGIN:textproc/linux-scim-libs @pkgdep @comment $FreeBSD: ports/print/acroread8/pkg-plist,v 1.2 2008/04/13 18:36:28 hrs Exp $ [snip] TFC On Tue, Nov 18, 2008 at 12:51 AM, Mel [EMAIL PROTECTED] wrote: On Tuesday 18 November 2008 05:18:37 Mel wrote: On Monday 17 November 2008 22:15:32 Tsu-Fan Cheng wrote: Hi Mel, thank you for your help, now I recompile pkg_install and run pkg_delete again, under print/acroread8 it still coredump. here is the result: # gdb pkg_delete pkg_delete.core GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-marcel-freebsd... Core was generated by `pkg_delete'. Program terminated with signal 11, Segmentation fault. Reading symbols from /lib/libmd.so.4...done. Loaded symbols for /lib/libmd.so.4 Reading symbols from /lib/libc.so.7...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /libexec/ld-elf.so.1...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x2815dae6 in strcmp () from /lib/libc.so.7 (gdb) bt #0 0x2815dae6 in strcmp () from /lib/libc.so.7 #1 0x0804b50c in isinstalledpkg (name=0x0) at /usr/src/usr.sbin/pkg_install/lib/match.c:374 There's the culprit. strcmp called on a null pointer. The reason is that the +CONTENTS file contains corrupted data. Most likely a @pkgdep line without a package name. Could you show the output of: grep @pkgdep /var/db/pkg/acroread8-8.1.2_2/+CONTENTS Actually, considering it comes from undepend, could you also include: cat /var/db/pkg/acroread8-8.1.2_2/+REQUIRED_BY -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pkg_delete core dump
On Tuesday 18 November 2008 13:37:11 Tsu-Fan Cheng wrote:
Hi Mel,
the link to download the +CONTENTS file is here
http://www.megaupload.com/?d=YDKFRCZG, and you know what? I don't have
+REQUIRED_BY file. thanks!!
there is a empty entry in the +CONTENTS file:
[snip]
@pkgdep linux-scim-libs-1.4.4
@comment DEPORIGIN:textproc/linux-scim-libs
@pkgdep
@comment $FreeBSD: ports/print/acroread8/pkg-plist,v 1.2 2008/04/13
18:36:28 hrs Exp $
That's definetely the cause of the crash. The patch below should guard against
pkg_delete crashing.
How this line got created in the first place, is very weird.
I would run:
grep -E '^@(pkgdep|name)[[:space:]]*$' /var/db/pkg/*/+CONTENTS
Which would show all dependency lines and name directives that are empty.
Maybe there's a common factor. For the moment my money is on linux-nvu as
that would be the dependency that belongs at the empty spot:
# make -C /usr/ports/print/acroread8 actual-package-depends | sort -u -t : -k
2
linux-atk-1.9.1:accessibility/linux-atk
linux-glib2-2.6.6_1:devel/linux-glib2
linux_base-fc-4_13:emulators/linux_base-fc4
linux-cairo-1.0.2:graphics/linux-cairo
linux-jpeg-6b.34:graphics/linux-jpeg
linux-png-1.2.8_2:graphics/linux-png
linux-tiff-3.7.1:graphics/linux-tiff
hicolor-icon-theme-0.10_2:misc/hicolor-icon-theme
acroreadwrapper-0.0.20080906:print/acroreadwrapper
linux-expat-1.95.8:textproc/linux-expat
linux-scim-libs-1.4.4:textproc/linux-scim-libs
linux-nvu-1.0:www/linux-nvu
linux-fontconfig-2.2.3_7:x11-fonts/linux-fontconfig
linux-hicolor-icon-theme-0.5_1:x11-themes/linux-hicolor-icon-theme
linux-gtk2-2.6.10:x11-toolkits/linux-gtk2
linux-pango-1.10.2:x11-toolkits/linux-pango
linux-xorg-libs-6.8.2_5:x11/linux-xorg-libs
--
Mel
Index: plist.c
===
RCS file: /home/ncvs/src/usr.sbin/pkg_install/lib/plist.c,v
retrieving revision 1.52
diff -u -r1.52 plist.c
--- plist.c 28 Mar 2007 05:33:52 - 1.52
+++ plist.c 18 Nov 2008 12:51:02 -
@@ -31,6 +31,11 @@
{
PackingList tmp;
+if( arg == NULL || arg[0] == '\0' )
+{
+ warnx(Invalid packing list line ignored);
+ return;
+}
tmp = new_plist_entry();
tmp-name = copy_string(arg);
tmp-type = type;
@@ -61,6 +66,11 @@
{
PackingList tmp;
+if( arg == NULL || arg[0] == '\0' )
+{
+ warnx(Invalid packing list line ignored);
+ return;
+}
tmp = new_plist_entry();
tmp-name = copy_string(arg);
tmp-type = type;
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pkg_delete core dump
it works!! thanks Mel.
TFC
On Tue, Nov 18, 2008 at 8:16 AM, Mel
[EMAIL PROTECTED] wrote:
On Tuesday 18 November 2008 13:37:11 Tsu-Fan Cheng wrote:
Hi Mel,
the link to download the +CONTENTS file is here
http://www.megaupload.com/?d=YDKFRCZG, and you know what? I don't have
+REQUIRED_BY file. thanks!!
there is a empty entry in the +CONTENTS file:
[snip]
@pkgdep linux-scim-libs-1.4.4
@comment DEPORIGIN:textproc/linux-scim-libs
@pkgdep
@comment $FreeBSD: ports/print/acroread8/pkg-plist,v 1.2 2008/04/13
18:36:28 hrs Exp $
That's definetely the cause of the crash. The patch below should guard against
pkg_delete crashing.
How this line got created in the first place, is very weird.
I would run:
grep -E '^@(pkgdep|name)[[:space:]]*$' /var/db/pkg/*/+CONTENTS
Which would show all dependency lines and name directives that are empty.
Maybe there's a common factor. For the moment my money is on linux-nvu as
that would be the dependency that belongs at the empty spot:
# make -C /usr/ports/print/acroread8 actual-package-depends | sort -u -t : -k
2
linux-atk-1.9.1:accessibility/linux-atk
linux-glib2-2.6.6_1:devel/linux-glib2
linux_base-fc-4_13:emulators/linux_base-fc4
linux-cairo-1.0.2:graphics/linux-cairo
linux-jpeg-6b.34:graphics/linux-jpeg
linux-png-1.2.8_2:graphics/linux-png
linux-tiff-3.7.1:graphics/linux-tiff
hicolor-icon-theme-0.10_2:misc/hicolor-icon-theme
acroreadwrapper-0.0.20080906:print/acroreadwrapper
linux-expat-1.95.8:textproc/linux-expat
linux-scim-libs-1.4.4:textproc/linux-scim-libs
linux-nvu-1.0:www/linux-nvu
linux-fontconfig-2.2.3_7:x11-fonts/linux-fontconfig
linux-hicolor-icon-theme-0.5_1:x11-themes/linux-hicolor-icon-theme
linux-gtk2-2.6.10:x11-toolkits/linux-gtk2
linux-pango-1.10.2:x11-toolkits/linux-pango
linux-xorg-libs-6.8.2_5:x11/linux-xorg-libs
--
Mel
Index: plist.c
===
RCS file: /home/ncvs/src/usr.sbin/pkg_install/lib/plist.c,v
retrieving revision 1.52
diff -u -r1.52 plist.c
--- plist.c 28 Mar 2007 05:33:52 - 1.52
+++ plist.c 18 Nov 2008 12:51:02 -
@@ -31,6 +31,11 @@
{
PackingList tmp;
+if( arg == NULL || arg[0] == '\0' )
+{
+ warnx(Invalid packing list line ignored);
+ return;
+}
tmp = new_plist_entry();
tmp-name = copy_string(arg);
tmp-type = type;
@@ -61,6 +66,11 @@
{
PackingList tmp;
+if( arg == NULL || arg[0] == '\0' )
+{
+ warnx(Invalid packing list line ignored);
+ return;
+}
tmp = new_plist_entry();
tmp-name = copy_string(arg);
tmp-type = type;
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
pkg_delete core dump
hi, during recompiling some ports, I found my pkg_delete core dump on some ports (not all of them), when it dumped, it has something like this (print/acroread8): # gdb pkg_delete pkg_delete.core GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-marcel-freebsd...(no debugging symbols found)... Core was generated by `pkg_delete'. Program terminated with signal 11, Segmentation fault. Reading symbols from /lib/libmd.so.4...(no debugging symbols found)...done. Loaded symbols for /lib/libmd.so.4 Reading symbols from /lib/libc.so.7...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x2815dae6 in strcmp () from /lib/libc.so.7 (gdb) bt full #0 0x2815dae6 in strcmp () from /lib/libc.so.7 No symbol table info available. #1 0x0804b50c in ?? () No symbol table info available. #2 0x0810b1a0 in ?? () No symbol table info available. #3 0x in ?? () No symbol table info available. #4 0x in ?? () No symbol table info available. #5 0x in ?? () No symbol table info available. #6 0x in ?? () No symbol table info available. #7 0x in ?? () No symbol table info available. #8 0x in ?? () No symbol table info available. #9 0x in ?? () No symbol table info available. #10 0x in ?? () No symbol table info available. #11 0x0810b180 in ?? () ---Type return to continue, or q return to quit--- No symbol table info available. #12 0xbfbfd968 in ?? () No symbol table info available. #13 0x0804adc5 in ?? () No symbol table info available. #14 0x in ?? () No symbol table info available. #15 0x000c in ?? () No symbol table info available. #16 0x03e1 in ?? () No symbol table info available. #17 0x28174af5 in fwrite () from /lib/libc.so.7 No symbol table info available. Previous frame inner to this frame (corrupt stack?) (gdb) any idea?? thanks!! TFC ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pkg_delete core dump
On Monday 17 November 2008 20:15:46 Tsu-Fan Cheng wrote: hi, during recompiling some ports, I found my pkg_delete core dump on some ports (not all of them), when it dumped, it has something like this (print/acroread8): # gdb pkg_delete pkg_delete.core GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-marcel-freebsd...(no debugging symbols found)... Core was generated by `pkg_delete'. Program terminated with signal 11, Segmentation fault. Reading symbols from /lib/libmd.so.4...(no debugging symbols found)...done. Loaded symbols for /lib/libmd.so.4 Reading symbols from /lib/libc.so.7...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x2815dae6 in strcmp () from /lib/libc.so.7 (gdb) bt full #0 0x2815dae6 in strcmp () from /lib/libc.so.7 No symbol table info available. #1 0x0804b50c in ?? () No symbol table info available. snip incomplete backtrace You will have to recompile pkg_delete with debug symbols to get any idea. To do so, do the following (providing you have sources in /usr/src): cd /usr/src/usr.sbin/pkg_install make clean make obj make DEBUG_FLAGS='-ggdb' depend make DEBUG_FLAGS='-ggdb' all install If this gives errors, it's best to do a full buildworld/installworld. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pkg_delete core dump
Hi Mel, thank you for your help, now I recompile pkg_install and run pkg_delete again, under print/acroread8 it still coredump. here is the result: # gdb pkg_delete pkg_delete.core GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-marcel-freebsd... Core was generated by `pkg_delete'. Program terminated with signal 11, Segmentation fault. Reading symbols from /lib/libmd.so.4...done. Loaded symbols for /lib/libmd.so.4 Reading symbols from /lib/libc.so.7...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /libexec/ld-elf.so.1...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x2815dae6 in strcmp () from /lib/libc.so.7 (gdb) bt #0 0x2815dae6 in strcmp () from /lib/libc.so.7 #1 0x0804b50c in isinstalledpkg (name=0x0) at /usr/src/usr.sbin/pkg_install/lib/match.c:374 #2 0x0804adc5 in requiredby (pkgname=0x0, list=0xbfbfe1a8, strict=0, filter=0) at /usr/src/usr.sbin/pkg_install/lib/deps.c:202 #3 0x08049c14 in undepend (p=0x0, pkgname=0x810b180 acroread8-8.1.2_2) at /usr/src/usr.sbin/pkg_install/delete/perform.c:385 #4 0x0804a769 in pkg_do (pkg=0x810b180 acroread8-8.1.2_2) at /usr/src/usr.sbin/pkg_install/delete/perform.c:286 #5 0x0804a981 in pkg_perform (pkgs=0x810c060) at /usr/src/usr.sbin/pkg_install/delete/perform.c:112 #6 0x08049b2a in real_main (argc=3, argv=0xbfbfeb60) at /usr/src/usr.sbin/pkg_install/delete/main.c:163 #7 0x0804ab58 in main (argc=3, argv=0xbfbfeb60) at /usr/src/usr.sbin/pkg_install/lib/pkgwrap.c:88 (gdb) bt full #0 0x2815dae6 in strcmp () from /lib/libc.so.7 No symbol table info available. #1 0x0804b50c in isinstalledpkg (name=0x0) at /usr/src/usr.sbin/pkg_install/lib/match.c:374 result = Variable result is not available. (gdb) up #1 0x0804b50c in isinstalledpkg (name=0x0) at /usr/src/usr.sbin/pkg_install/lib/match.c:374 374 if (strcmp(memo-iip_name, name) == 0) (gdb) should I do a full buildworld/installworld? TFC On Mon, Nov 17, 2008 at 2:36 PM, Mel [EMAIL PROTECTED] wrote: On Monday 17 November 2008 20:15:46 Tsu-Fan Cheng wrote: hi, during recompiling some ports, I found my pkg_delete core dump on some ports (not all of them), when it dumped, it has something like this (print/acroread8): # gdb pkg_delete pkg_delete.core GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-marcel-freebsd...(no debugging symbols found)... Core was generated by `pkg_delete'. Program terminated with signal 11, Segmentation fault. Reading symbols from /lib/libmd.so.4...(no debugging symbols found)...done. Loaded symbols for /lib/libmd.so.4 Reading symbols from /lib/libc.so.7...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x2815dae6 in strcmp () from /lib/libc.so.7 (gdb) bt full #0 0x2815dae6 in strcmp () from /lib/libc.so.7 No symbol table info available. #1 0x0804b50c in ?? () No symbol table info available. snip incomplete backtrace You will have to recompile pkg_delete with debug symbols to get any idea. To do so, do the following (providing you have sources in /usr/src): cd /usr/src/usr.sbin/pkg_install make clean make obj make DEBUG_FLAGS='-ggdb' depend make DEBUG_FLAGS='-ggdb' all install If this gives errors, it's best to do a full buildworld/installworld. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pkg_delete core dump
On Monday 17 November 2008 22:15:32 Tsu-Fan Cheng wrote: Hi Mel, thank you for your help, now I recompile pkg_install and run pkg_delete again, under print/acroread8 it still coredump. here is the result: # gdb pkg_delete pkg_delete.core GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-marcel-freebsd... Core was generated by `pkg_delete'. Program terminated with signal 11, Segmentation fault. Reading symbols from /lib/libmd.so.4...done. Loaded symbols for /lib/libmd.so.4 Reading symbols from /lib/libc.so.7...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /libexec/ld-elf.so.1...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x2815dae6 in strcmp () from /lib/libc.so.7 (gdb) bt #0 0x2815dae6 in strcmp () from /lib/libc.so.7 #1 0x0804b50c in isinstalledpkg (name=0x0) at /usr/src/usr.sbin/pkg_install/lib/match.c:374 There's the culprit. strcmp called on a null pointer. The reason is that the +CONTENTS file contains corrupted data. Most likely a @pkgdep line without a package name. Could you show the output of: grep @pkgdep /var/db/pkg/acroread8-8.1.2_2/+CONTENTS -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pkg_delete core dump
On Tuesday 18 November 2008 05:18:37 Mel wrote: On Monday 17 November 2008 22:15:32 Tsu-Fan Cheng wrote: Hi Mel, thank you for your help, now I recompile pkg_install and run pkg_delete again, under print/acroread8 it still coredump. here is the result: # gdb pkg_delete pkg_delete.core GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-marcel-freebsd... Core was generated by `pkg_delete'. Program terminated with signal 11, Segmentation fault. Reading symbols from /lib/libmd.so.4...done. Loaded symbols for /lib/libmd.so.4 Reading symbols from /lib/libc.so.7...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /libexec/ld-elf.so.1...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x2815dae6 in strcmp () from /lib/libc.so.7 (gdb) bt #0 0x2815dae6 in strcmp () from /lib/libc.so.7 #1 0x0804b50c in isinstalledpkg (name=0x0) at /usr/src/usr.sbin/pkg_install/lib/match.c:374 There's the culprit. strcmp called on a null pointer. The reason is that the +CONTENTS file contains corrupted data. Most likely a @pkgdep line without a package name. Could you show the output of: grep @pkgdep /var/db/pkg/acroread8-8.1.2_2/+CONTENTS Actually, considering it comes from undepend, could you also include: cat /var/db/pkg/acroread8-8.1.2_2/+REQUIRED_BY -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Strange Core Dump Error Message on a FreeBSD6.3 System
I am running some C code I wrote on a couple of FreeBSD6.3 systems, one of which has never exhibited this message and the other has now done it twice in about 6 months. The error is as follows: mem.c:877: INSIST(ctx-stats[i].gets == 0U) failed. Abort trap (core dumped) Something obviously is wrong regarding memory allocation but why this one system? Is there anything I can look for in netstat -m that might help me solve the puzzle? Thanks. Martin McCormick WB5AGZ Stillwater, OK Systems Engineer OSU Information Technology Department Telecommunications Services Group ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Strange Core Dump Error Message on a FreeBSD6.3 System
On Tue, Oct 07, 2008 at 04:15:24PM -0500, Martin McCormick wrote: I am running some C code I wrote on a couple of FreeBSD6.3 systems, one of which has never exhibited this message and the other has now done it twice in about 6 months. The error is as follows: mem.c:877: INSIST(ctx-stats[i].gets == 0U) failed. Abort trap (core dumped) Something obviously is wrong regarding memory allocation but why this one system? Is there anything I can look for in netstat -m that might help me solve the puzzle? Thanks. Try freebsd-hackers for this sort of question. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
brain-fault: core dump.
A few days ago I dl'd the OOo-2.4.1 and now need some clues how to install the tarball. I tried #pkg_add -rv [OOo-tarball] it failed. ...So is there some quick fix? tia, gary -- Gary Kline [EMAIL PROTECTED] http://www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: brain-fault: core dump.
A few days ago I dl'd the OOo-2.4.1 and now need some clues how to install the tarball. I tried #pkg_add -rv [OOo-tarball] it failed. ...So is there some quick fix? tia, gary http://view.samurajdata.se/ http://porting.openoffice.org/freebsd/#howto ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Cannot get kernel core dump
Hello! I'm trying to report a problem which involves kernel panic, but I cannot get a core dump. The system is 7.0-STABLE from June 18th. I've set the following in /etc/rc.conf (and of course rebooted, even several times): dumpdev=/dev/ad0s1b dumpdir=/home/crash The machine has 512 MB RAM and swap partition is also 512 MB, but according to dumpon(8) this shouldn't be a problem, because hw.physmem is still somewhat smaller than the swap partition: bsd# sysctl hw.physmem hw.physmem: 527863808 bsd# swapinfo Device 1K-blocks UsedAvail Capacity /dev/ad0s1b5242880 524288 0% /home partition, where I've created the crash directory, has 55 GB free space. When the machine boots up, it dutifully reports: kernel dumps on /dev/ad0s1b Then I do the thing that causes the panic. System prints the panic message and hangs. Only thing left to do is press the reset button. On next boot, the log says savecore: no dumps found When the system panics and prints the panic message, it doesn't say anything about saving the coredump. I haven't had a kernel panic for a long time, but I seem to remember that in the past there was some kind of message to that effect. Are there known conditions under which the core dump really isn't recorded, or am I simply missing something obvious? -- Toomas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cannot get kernel core dump
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Toomas Aas wrote: | Hello! | | I'm trying to report a problem which involves kernel panic, but I cannot get a | core dump. The system is 7.0-STABLE from June 18th. | | I've set the following in /etc/rc.conf (and of course rebooted, even several | times): | dumpdev=/dev/ad0s1b | dumpdir=/home/crash | | The machine has 512 MB RAM and swap partition is also 512 MB, but according to | dumpon(8) this shouldn't be a problem, because hw.physmem is still somewhat | smaller than the swap partition: | | bsd# sysctl hw.physmem | hw.physmem: 527863808 | | bsd# swapinfo | Device 1K-blocks UsedAvail Capacity | /dev/ad0s1b5242880 524288 0% | | /home partition, where I've created the crash directory, has 55 GB free space. | | When the machine boots up, it dutifully reports: | kernel dumps on /dev/ad0s1b | | Then I do the thing that causes the panic. System prints the panic message | and hangs. Only thing left to do is press the reset button. On next boot, the | log says | savecore: no dumps found | | When the system panics and prints the panic message, it doesn't say anything | about saving the coredump. I haven't had a kernel panic for a long time, but | I seem to remember that in the past there was some kind of message to that | effect. | | Are there known conditions under which the core dump really isn't recorded, or | am I simply missing something obvious? Yes, if the panic occurs before the filesystem supposed to contain the crash dumps is mounted. Is it the case? | | -- | Toomas | ___ | freebsd-questions@freebsd.org mailing list | http://lists.freebsd.org/mailman/listinfo/freebsd-questions | To unsubscribe, send any mail to [EMAIL PROTECTED] - -- Pietro Cerutti [EMAIL PROTECTED] PGP Public Key: http://gahr.ch/pgp -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) iEYEAREKAAYFAkhiVTgACgkQwMJqmJVx9454AwCgowIDacy0X33iBwbC0QRVCYjw zGcAnig8zjnlrq1njlwqO7pJOGIyOV3O =4wCh -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Panic when disconnecting Coolpix L5 (was: Cannot get kernel core dump)
Wednesday 25 June 2008 17:24:58 kirjutas Pietro Cerutti: Toomas Aas wrote: | Are there known conditions under which the core dump really isn't | recorded, or am I simply missing something obvious? Yes, if the panic occurs before the filesystem supposed to contain the crash dumps is mounted. Is it the case? No, the panic occurs when the system is in full multi-user mode and all filesystems are mounted, including /home where I have configured the crash dumps. Swap partition /dev/ad0s1b is also active. However, it just occurred to me that the system actually goes somewhat awry even before the panic occurs, so perhaps this is why the core dump is not recorded. The sequence of events is like this: 1. I attach a digital camera (Nikon Coolpix L5) via USB to my computer, which has Asrock K7S41GX motherboard, with onboard SiS 5571 USB controller. The camera is set to 'Mass storage' mode. 2. The system seems to recognize the camera with some success: Jun 25 16:35:48 bsd root: Unknown USB device: vendor 0x04b0 product 0x020d bus uhub1 Jun 25 16:35:48 bsd kernel: umass0: NIKON NIKON DSC COOLPIX L5, class 0/0, rev 1.10/1.00, addr 2 on uhub1 Jun 25 16:35:48 bsd kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Jun 25 16:35:48 bsd kernel: da0: NIKON DSC COOLPIX L5 Removable Direct Access SCSI-2 device Jun 25 16:35:48 bsd kernel: da0: 1.000MB/s transfers Jun 25 16:35:48 bsd kernel: da0: 485MB (994304 512 byte sectors: 64H 32S/T 485C) However, at that point the machine pretty much stops responding. Clicking any icons in KDE has no effect. I can switch to another tty by pressing for example Alt+F3, but I cannot log in there (the login prompt appears but I can't type my login name). 3. I disconnect the camera and kernel panics. umass0: BBB reset failed, IOERROR umass0: BBB bulk-in clear stall failed, IOERROR umass0: at uhub1, port 2 (addr 2) disconnected (da0:umass-sim0:0:0:0): lost device (da0:dead-sim0):0:0:0): Synchronize cache failed, status == 0x39, scsi status == 0x0 Fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code = supervisor write, page not present instruction pointer = 0x20:0xc043fb4b stack pointer = 0x28:0xd4cd4adc frame pointer = 0x28:0xd4cd4af8 code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt ennabled, resume, IOPL = 0 current process = 2 (g_event) trap number = 12 panic: page fault Uptime: 1m 20s Instruction pointer and current process are always identical, I haven't compared all the other information. $ nm -n /boot/kernel/kernel | grep c043fb c043fb10 T xpt_done Note that I haven't mounted the camera before disconnecting, so it's probably not the 'well known problem' described on Jeremy Chadwick's wiki page. Any further ideas on how to debug such problem or which mailing list is more appropriate? Thanks a lot, -- Toomas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Apache -- Analyzing core dump?
Chris Maness wrote: Chris Maness wrote: I used to analyze core dumps with tnos to debug. It has been a coon's age since I've done such. I am having apache crash and core dump. There isn't any error info in the log files. Where is the core dumped to (the main log tells me the core has been dumped)? How do I analyze this dump file to find out what went wrong? Do I have to compile apache with debug features turned on to do this? I am referring to my previous thread: apache+mod_ssl-1.3.41+2.8.31 crashing with mod_php5 I was able to find my old e-mails on debugging tnos. I used gdb. Per the gdb man page I was able to figure out how to check the core file. Here is the output: GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-marcel-freebsd...(no debugging symbols found)... Core was generated by `httpd'. Program terminated with signal 11, Segmentation fault. Reading symbols from /lib/libcrypt.so.4...(no debugging symbols found)...done. Loaded symbols for /lib/libcrypt.so.4 Reading symbols from /usr/local/lib/libmm.so.14...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libmm.so.14 Reading symbols from /usr/local/lib/libexpat.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libexpat.so.6 Reading symbols from /lib/libc.so.7...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /usr/local/libexec/apache/mod_mmap_static.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/libexec/apache/mod_mmap_static.so Reading symbols from /usr/local/libexec/apache/mod_vhost_alias.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/libexec/apache/mod_vhost_alias.so Reading symbols from /usr/local/libexec/apache/mod_env.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/libexec/apache/mod_env.so Reading symbols from /usr/local/libexec/apache/mod_define.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/libexec/apache/mod_define.so Reading symbols from /usr/local/libexec/apache/mod_log_config.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/libexec/apache/mod_log_config.so Reading symbols from /usr/local/libexec/apache/mod_mime_magic.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/libexec/apache/mod_mime_magic.so Reading symbols from /usr/local/libexec/apache/mod_mime.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/libexec/apache/mod_mime.so Reading symbols from /usr/local/libexec/apache/mod_negotiation.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/libexec/apache/mod_negotiation.so Reading symbols from /usr/local/libexec/apache/mod_status.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/libexec/apache/mod_status.so Reading symbols from /usr/local/libexec/apache/mod_info.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/libexec/apache/mod_info.so Reading symbols from /usr/local/libexec/apache/mod_include.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/libexec/apache/mod_include.so Reading symbols from /usr/local/libexec/apache/mod_autoindex.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/libexec/apache/mod_autoindex.so Reading symbols from /usr/local/libexec/apache/mod_dir.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/libexec/apache/mod_dir.so Reading symbols from /usr/local/libexec/apache/mod_cgi.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/libexec/apache/mod_cgi.so Reading symbols from /usr/local/libexec/apache/mod_asis.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/libexec/apache/mod_asis.so Reading symbols from /usr/local/libexec/apache/mod_imap.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/libexec/apache/mod_imap.so Reading symbols from /usr/local/libexec/apache/mod_actions.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/libexec/apache/mod_actions.so Reading symbols from /usr/local/libexec/apache/mod_speling.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/libexec/apache/mod_speling.so Reading symbols from /usr/local/libexec/apache/mod_userdir.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/libexec/apache/mod_userdir.so Reading symbols from /usr/local/libexec/apache/mod_alias.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/libexec/apache/mod_alias.so Reading symbols from /usr/local
Apache -- Analyzing core dump?
I used to analyze core dumps with tnos to debug. It has been a coon's age since I've done such. I am having apache crash and core dump. There isn't any error info in the log files. Where is the core dumped to (the main log tells me the core has been dumped)? How do I analyze this dump file to find out what went wrong? Do I have to compile apache with debug features turned on to do this? I am referring to my previous thread: apache+mod_ssl-1.3.41+2.8.31 crashing with mod_php5 -- Chris Maness (909) 223-9179 http://www.chrismaness.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Apache -- Analyzing core dump?
Chris Maness wrote: I used to analyze core dumps with tnos to debug. It has been a coon's age since I've done such. I am having apache crash and core dump. There isn't any error info in the log files. Where is the core dumped to (the main log tells me the core has been dumped)? How do I analyze this dump file to find out what went wrong? Do I have to compile apache with debug features turned on to do this? I am referring to my previous thread: apache+mod_ssl-1.3.41+2.8.31 crashing with mod_php5 I was able to find my old e-mails on debugging tnos. I used gdb. Per the gdb man page I was able to figure out how to check the core file. Here is the output: GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-marcel-freebsd...(no debugging symbols found)... Core was generated by `httpd'. Program terminated with signal 11, Segmentation fault. Reading symbols from /lib/libcrypt.so.4...(no debugging symbols found)...done. Loaded symbols for /lib/libcrypt.so.4 Reading symbols from /usr/local/lib/libmm.so.14...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libmm.so.14 Reading symbols from /usr/local/lib/libexpat.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libexpat.so.6 Reading symbols from /lib/libc.so.7...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /usr/local/libexec/apache/mod_mmap_static.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/libexec/apache/mod_mmap_static.so Reading symbols from /usr/local/libexec/apache/mod_vhost_alias.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/libexec/apache/mod_vhost_alias.so Reading symbols from /usr/local/libexec/apache/mod_env.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/libexec/apache/mod_env.so Reading symbols from /usr/local/libexec/apache/mod_define.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/libexec/apache/mod_define.so Reading symbols from /usr/local/libexec/apache/mod_log_config.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/libexec/apache/mod_log_config.so Reading symbols from /usr/local/libexec/apache/mod_mime_magic.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/libexec/apache/mod_mime_magic.so Reading symbols from /usr/local/libexec/apache/mod_mime.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/libexec/apache/mod_mime.so Reading symbols from /usr/local/libexec/apache/mod_negotiation.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/libexec/apache/mod_negotiation.so Reading symbols from /usr/local/libexec/apache/mod_status.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/libexec/apache/mod_status.so Reading symbols from /usr/local/libexec/apache/mod_info.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/libexec/apache/mod_info.so Reading symbols from /usr/local/libexec/apache/mod_include.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/libexec/apache/mod_include.so Reading symbols from /usr/local/libexec/apache/mod_autoindex.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/libexec/apache/mod_autoindex.so Reading symbols from /usr/local/libexec/apache/mod_dir.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/libexec/apache/mod_dir.so Reading symbols from /usr/local/libexec/apache/mod_cgi.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/libexec/apache/mod_cgi.so Reading symbols from /usr/local/libexec/apache/mod_asis.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/libexec/apache/mod_asis.so Reading symbols from /usr/local/libexec/apache/mod_imap.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/libexec/apache/mod_imap.so Reading symbols from /usr/local/libexec/apache/mod_actions.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/libexec/apache/mod_actions.so Reading symbols from /usr/local/libexec/apache/mod_speling.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/libexec/apache/mod_speling.so Reading symbols from /usr/local/libexec/apache/mod_userdir.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/libexec/apache/mod_userdir.so Reading symbols from /usr/local/libexec/apache/mod_alias.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/libexec/apache/mod_alias.so Reading symbols from /usr/local/libexec/apache
Core dump
A program that I use has started giving me this error message when I try to load it: Segmentation fault: 11 (core dumped) Can someone give me a heads up on what's going on here. I've done a reinstall to no avail. Rem ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Core dump
On 2007-10-31 15:32, Rem P Roberti [EMAIL PROTECTED] wrote: A program that I use has started giving me this error message when I try to load it: Segmentation fault: 11 (core dumped) Can someone give me a heads up on what's going on here. I've done a reinstall to no avail. Is there any reason why you can't tell us the name of the program? The more details you provide, the easier it is going to be for someone else to help you troubleshoot the problem. Do you have a debug-build of the program around? If you do, you can use gdb(1) to try to grab a stack trace of the program, and with a little luck and a bit of effort, it may even be possible to find out the root cause of the segmentation fault. Giorgos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Core dump
On Wed, Oct 31, 2007 at 03:32:10PM -0700, Rem P Roberti wrote: A program that I use has started giving me this error message when I try to load it: Segmentation fault: 11 (core dumped) This means that the program has either tried to read from a part of the memory that it isn't allowed to access, or it has tried to write to a memory page that is marked read-only. Can someone give me a heads up on what's going on here. I've done a reinstall to no avail. It is a bug in the program. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpgQTPsLfEjo.pgp Description: PGP signature
Re: Core dump
On 2007.11.01 00:39:52 +, Roland Smith wrote: On Wed, Oct 31, 2007 at 03:32:10PM -0700, Rem P Roberti wrote: A program that I use has started giving me this error message when I try to load it: Segmentation fault: 11 (core dumped) This means that the program has either tried to read from a part of the memory that it isn't allowed to access, or it has tried to write to a memory page that is marked read-only. Can someone give me a heads up on what's going on here. I've done a reinstall to no avail. It is a bug in the program. Ok. Well, the program is Fldigi, which is an amateur radio program, but now Skype is doing the same thing. Interestingly, Skype started dumping core after I read UPDATING and made the changes suggested to get it running correctly. Rem ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Core dump
On Thu, 1 Nov 2007 00:39:52 +0100 Roland Smith [EMAIL PROTECTED] wrote: On Wed, Oct 31, 2007 at 03:32:10PM -0700, Rem P Roberti wrote: A program that I use has started giving me this error message when I try to load it: Segmentation fault: 11 (core dumped) Hey, it's Halloween! ;) This means that the program has either tried to read from a part of the memory that it isn't allowed to access, or it has tried to write to a memory page that is marked read-only. Rem, if you have updated that program recently, you may have installed a version that introduced a new bug. It could also happen when one of the libraries loaded by that program have been updated, and also introduced such a bug (hint: ldd(1) for a list of dynamically loaded libraries). Can someone give me a heads up on what's going on here. I've done a reinstall to no avail. It is a bug in the program. Yes, but if it doesn't always happen at the same location of the program, or even starts to affect other programs, seemingly randomly, you may also have a hardware problem, like faulty RAM, overheating CPU, bad PSU etc... Check your RAM with the ports sysutils/memtest86 and sysutils/memtest if you have doubts. -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SMP options and core dump failure
On Tue, July 3, 2007 02:59, Yong Rao wrote: Hello, We have a problem with SMP kernel. It could not dump out core when the crash happens. Which version of FreeBSD? -Current? better ask in [EMAIL PROTECTED] or file a PR. http://www.freebsd.org/send-pr.html Rgds, Patrick I am able to isolate the problem to kernel configurations which have SMP enabled when used with 2 cpus. With ONE cpu the core dump works ok. I built the kernel with GENERIC, and deliberately crash the kernel (for testing purpose). The core dump works fine. Only added the options SMP and crashed the kernel, then prior to any pages being dumped out, it hangs there. Has someone successfully core dumped on a system using SMP kernel with multiple CPUs? I tried on two different boxes (different motherboards, CPUs and hard disks). Both got failed. I tried to enable the DDB, but don't know what to look for when it goes into ddb. Appreciate any pointers. a) The CPU information is CPU: Dual Core AMD Opteron(tm) Processor 280 (2405.47-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x20f12 Stepping = 2 Features=0x178bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE ,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,S SE,SSE2,HTT Features2=0x1SSE3 AMD Features=0xe2500800SYSCALL,NX,MMX+,FFXSR,LM,3DNow+,3DNow AMD Features2=0x3LAHF,CMP Cores per package: 2 b) We also tried on another mother board, which has 2 CPUs. The CPU information is below. CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2800.11-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf29 Stepping = 9 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE ,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x4400CNTX-ID,b14 real memory = 2147418112 (2047 MB) avail memory = 2096300032 (1999 MB) ACPI APIC Table: A M I OEMAPIC FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 6 c) The following are the prints when the dump hung. mem dump: start address = 0x4352, len=0x30 Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x4352 fault code = supervisor read, page not present instruction pointer = 0x20:0xc9e9fc92 stack pointer = 0x28:0xebdbdbdc frame pointer = 0x28:0xebdbdbf8 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 74231 (pnicdbg) trap number = 12 panic: page fault cpuid = 1 Uptime: 1d18h27m42s Dumping 4030 MB (2 chunks) chunk 0: 1MB (154 pages) ... ok chunk 1: 4031MB (1031776 pages) (stopped and hung here) Thanks, Yong Rao Force10 Networks Inc. 350 Holger Way San Jose, CA 95132 408 571 6317 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: SMP options and core dump failure
Thanks, Patrick! It is not the current version. It is FreeBSD localhost.localdomain 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jun 15 11:02:24 PDT 2007 Thanks, Yong -Original Message- From: Gelsema, P (Patrick) - FreeBSD [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 03, 2007 1:23 AM To: Yong Rao Cc: [EMAIL PROTECTED] Subject: Re: SMP options and core dump failure On Tue, July 3, 2007 02:59, Yong Rao wrote: Hello, We have a problem with SMP kernel. It could not dump out core when the crash happens. Which version of FreeBSD? -Current? better ask in [EMAIL PROTECTED] or file a PR. http://www.freebsd.org/send-pr.html Rgds, Patrick I am able to isolate the problem to kernel configurations which have SMP enabled when used with 2 cpus. With ONE cpu the core dump works ok. I built the kernel with GENERIC, and deliberately crash the kernel (for testing purpose). The core dump works fine. Only added the options SMP and crashed the kernel, then prior to any pages being dumped out, it hangs there. Has someone successfully core dumped on a system using SMP kernel with multiple CPUs? I tried on two different boxes (different motherboards, CPUs and hard disks). Both got failed. I tried to enable the DDB, but don't know what to look for when it goes into ddb. Appreciate any pointers. a) The CPU information is CPU: Dual Core AMD Opteron(tm) Processor 280 (2405.47-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x20f12 Stepping = 2 Features=0x178bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE ,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,S SE,SSE2,HTT Features2=0x1SSE3 AMD Features=0xe2500800SYSCALL,NX,MMX+,FFXSR,LM,3DNow+,3DNow AMD Features2=0x3LAHF,CMP Cores per package: 2 b) We also tried on another mother board, which has 2 CPUs. The CPU information is below. CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2800.11-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf29 Stepping = 9 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE ,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x4400CNTX-ID,b14 real memory = 2147418112 (2047 MB) avail memory = 2096300032 (1999 MB) ACPI APIC Table: A M I OEMAPIC FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 6 c) The following are the prints when the dump hung. mem dump: start address = 0x4352, len=0x30 Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x4352 fault code = supervisor read, page not present instruction pointer = 0x20:0xc9e9fc92 stack pointer = 0x28:0xebdbdbdc frame pointer = 0x28:0xebdbdbf8 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 74231 (pnicdbg) trap number = 12 panic: page fault cpuid = 1 Uptime: 1d18h27m42s Dumping 4030 MB (2 chunks) chunk 0: 1MB (154 pages) ... ok chunk 1: 4031MB (1031776 pages) (stopped and hung here) Thanks, Yong Rao Force10 Networks Inc. 350 Holger Way San Jose, CA 95132 408 571 6317 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
SMP options and core dump failure
Hello, We have a problem with SMP kernel. It could not dump out core when the crash happens. I am able to isolate the problem to kernel configurations which have SMP enabled when used with 2 cpus. With ONE cpu the core dump works ok. I built the kernel with GENERIC, and deliberately crash the kernel (for testing purpose). The core dump works fine. Only added the options SMP and crashed the kernel, then prior to any pages being dumped out, it hangs there. Has someone successfully core dumped on a system using SMP kernel with multiple CPUs? I tried on two different boxes (different motherboards, CPUs and hard disks). Both got failed. I tried to enable the DDB, but don't know what to look for when it goes into ddb. Appreciate any pointers. a) The CPU information is CPU: Dual Core AMD Opteron(tm) Processor 280 (2405.47-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x20f12 Stepping = 2 Features=0x178bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE ,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,S SE,SSE2,HTT Features2=0x1SSE3 AMD Features=0xe2500800SYSCALL,NX,MMX+,FFXSR,LM,3DNow+,3DNow AMD Features2=0x3LAHF,CMP Cores per package: 2 b) We also tried on another mother board, which has 2 CPUs. The CPU information is below. CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2800.11-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf29 Stepping = 9 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE ,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x4400CNTX-ID,b14 real memory = 2147418112 (2047 MB) avail memory = 2096300032 (1999 MB) ACPI APIC Table: A M I OEMAPIC FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 6 c) The following are the prints when the dump hung. mem dump: start address = 0x4352, len=0x30 Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x4352 fault code = supervisor read, page not present instruction pointer = 0x20:0xc9e9fc92 stack pointer = 0x28:0xebdbdbdc frame pointer = 0x28:0xebdbdbf8 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 74231 (pnicdbg) trap number = 12 panic: page fault cpuid = 1 Uptime: 1d18h27m42s Dumping 4030 MB (2 chunks) chunk 0: 1MB (154 pages) ... ok chunk 1: 4031MB (1031776 pages) (stopped and hung here) Thanks, Yong Rao Force10 Networks Inc. 350 Holger Way San Jose, CA 95132 408 571 6317 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: No core dump after panic
On 3/22/07, Rajkumar S [EMAIL PROTECTED] wrote: On 3/22/07, Simon Chang [EMAIL PROTECTED] wrote: Check out man savecore for a list of flags. Thanks, I will check that out. I have reinstalled and now starting from scratch to see if I can get the core dump of a panic. dumpdev=/dev/ad2s1b dumpdir=/var/crash savecore_flags=-v -z hw.physmem: 508989440 Device 1K-blocks UsedAvail Capacity /dev/ad2s1b7680000 768000 0% /dev/ad2s1d989M7.9M902M 1%/var My kernel panics immediately on boot up, before the disks are probed. After panic I boot with a different kernel to extract the core. But I get the following error during boot up. Checking for core dump on /dev/ad2s1b... unable to open bounds file, using 0 checking for kernel dump on device /dev/ad2s1b mediasize = 786432000 sectorsize = 512 magic mismatch on last dump header on /dev/ad2s1b savecore: no dumps found Any idea? raj ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: No core dump after panic
Well, this means that, since your previous kernel panicked but was not able to save a coredump, when you boot up from another kernel there is simply nothing there for savecore to recover. As a result savecore is reporting that there is nothing to recover for you. But that's the way to set it up. And you can ignore the unable to open bounds file message; it means that the bounds file wasn't there but it created it for you automatically. SC ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: No core dump after panic
Hi, Thanks for your reply! On 3/21/07, Simon Chang [EMAIL PROTECTED] wrote: From what you are saying it sounds like you are getting the panic on bootup. Is that correct? Yes. immediately on boot up. In looking through your config I don't see anything that really stands out (although I would use /var/crash for dumpdir, and you didn't specify savecore_flags). I did not use /var/crash because /var was small than RAM. So I manually changed the crash directory to /usr partition. I do not know how to set savecore flag. What else have you tried to get this kernel to boot? Do you have another kernel you were able to boot from? What about your exact hardware config? The panic happens only when safenet driver is complied in., GENERIC freebsd kernel boots up fine. I am using Axiomtek NA-1281A* I have reported the details about the panic in another mail+, raj * http://www.axiomtek.com.tw/Products/ViewProduct.asp?view=179 + http://lists.freebsd.org/pipermail/freebsd-questions/2007-March/145020.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: No core dump after panic
I did not use /var/crash because /var was small than RAM. So I manually changed the crash directory to /usr partition. I do not know how to set savecore flag. Check out man savecore for a list of flags. You normally set them in /etc/rc.conf by putting in a line like: savecore_flags=-v -z, where -v puts in extra debugging information and -z compresses the coredump so that you save some space. The panic happens only when safenet driver is complied in., GENERIC freebsd kernel boots up fine. I am using Axiomtek NA-1281A* I have reported the details about the panic in another mail+, Have you submitted a formal PR? I have to say that I have not had experience with that device or driver. What other responses have you gotten from people? SC ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: No core dump after panic
On 3/22/07, Simon Chang [EMAIL PROTECTED] wrote: Check out man savecore for a list of flags. Thanks, I will check that out. Have you submitted a formal PR? I have to say that I have not had experience with that device or driver. What other responses have you gotten from people? Yes, 110663, Sam Leffler the author of the driver has responded. I hope he will fix this problem. raj ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: No core dump after panic
Hey there, From what you are saying it sounds like you are getting the panic on bootup. Is that correct? In looking through your config I don't see anything that really stands out (although I would use /var/crash for dumpdir, and you didn't specify savecore_flags). What else have you tried to get this kernel to boot? Do you have another kernel you were able to boot from? What about your exact hardware config? More information would be helpful. SC ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
No core dump after panic
Hi, I am trying to get core dump of a kernel panic relating to safenet driver, so that I can file a meaning full PR or even try to debug myself. But I am not getting a core dump after panic. I have gone thorough the developers manual and I believe I have taken care of all the usual stuff. rc.conf dumpdev=/dev/ad2s1b dumpdir=/usr/local/crash sysctl hw.physmem hw.physmem: 508989440 swapinfo Device 1K-blocks UsedAvail Capacity /dev/ad2s1b 10485760 1048576 0% df -h | grep usr$ /dev/ad2s1f6.8G1.2G5.1G18%/usr The panic occurs before the disk drivers are loaded, ie just after network is probed. Could that be the reason? last couple of lines in dmesg while panic is as follows. rl7: RealTek 8139 10/100BaseTX port 0xac00-0xacff mem 0xf6007000-0xf60070ff i2miibus7: MII bus on rl7 rlphy7: RealTek internal media interface on miibus7 rlphy7: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl7: Ethernet address: 00:60:e0:04:29:e4 safe0 mem 0xf612-0xf6121fff irq 5 at device 10.0 on pci0 safe0: cannot allocate DMA tag device_attach: safe0 attach returned 6 re0: RealTek 8169S Single-chip Gigabit Ethernet port 0xb000-0xb0ff mem 0xf6120re0: could not allocate dma tag Fatal trap 12: page fault while in kernel mode fault virtual address = 0x60 fault code = supervisor read, page not present instruction pointer = 0x20:0xc0570ea5 stack pointer = 0x28:0xc0c20bd0 frame pointer = 0x28:0xc0c20be4 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 0 (swapper) trap number = 12 panic: page fault Uptime: 1s raj ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd 6.2 oracle php php-oci8 core dump
El martes 27 de febrero a las 11:16:44 CET, Dan Cojocar escribió: Hello all, I have oracle-xe, lang/php5, databases/linux-oracle-instantclient-basic, databases/linux-oracle-instantclient-sdk, databases/oracle8-client and databases/php5-oci8 following this howto: http://mrtenente.infosys.lt/blog/?p=22 all are installed without errors. But when I connect to oracle from php i get a core dump that i cannot access. I mention that I have compiled php with debug enabled. Can somebody suggest another setup? Or how to investigate this? I think databases/oracle8-client port is broken in 6.2-RELEASE. I have installed databases/tora port and it crashes with a core. In 6.1-RELEASE works well. My settings: WITHOUT_MYSQL=1 WITHOUT_PGSQL=1 WITHOUT_KDE=1 Regards -- http://personales.ya.com/banach pgpfkaqPeWLqP.pgp Description: PGP signature
freebsd 6.2 oracle php php-oci8 core dump
Hello all, I have oracle-xe, lang/php5, databases/linux-oracle-instantclient-basic, databases/linux-oracle-instantclient-sdk, databases/oracle8-client and databases/php5-oci8 following this howto: http://mrtenente.infosys.lt/blog/?p=22 all are installed without errors. But when I connect to oracle from php i get a core dump that i cannot access. I mention that I have compiled php with debug enabled. Can somebody suggest another setup? Or how to investigate this? Thank you, Dan gdb php php.core 12:07:12 GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-marcel-freebsd... Core was generated by `php'. Program terminated with signal 11, Segmentation fault. Reading symbols from /lib/libcrypt.so.3...done. Loaded symbols for /lib/libcrypt.so.3 Reading symbols from /lib/libm.so.4...done. Loaded symbols for /lib/libm.so.4 Reading symbols from /usr/local/lib/libxml2.so.5...done. Loaded symbols for /usr/local/lib/libxml2.so.5 Reading symbols from /lib/libz.so.3...done. Loaded symbols for /lib/libz.so.3 Reading symbols from /usr/local/lib/libiconv.so.3...done. Loaded symbols for /usr/local/lib/libiconv.so.3 Reading symbols from /lib/libc.so.6...done. Loaded symbols for /lib/libc.so.6 Reading symbols from /usr/local/lib/php/20060613-debug/oci8.so...done. Loaded symbols for /usr/local/lib/php/20060613-debug/oci8.so Reading symbols from /libexec/ld-elf.so.1...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x48b2116c in ?? () from /usr/local/lib/php/20060613-debug/oci8.so [New LWP 100042] (gdb) bt #0 0x48b2116c in ?? () from /usr/local/lib/php/20060613-debug/oci8.so Cannot access memory at address 0x196 (gdb) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Core Dump during 'portmanager'
G'day,
I'm having this problem with a broken port that keeps core dumping as I
attempt to upgrade my installed ports using portmanager on FreeBSD
v4.10-RELEASE-p24 #44. Is this a bug or just a bad port that needs to be
uninstalled?? Here's a snippet of the portmanager log before it core dumps.
00024 k3b-0.12.17 /sysutils/k3b
00023 pkg_install-devel-20040811 /sysutils/pkg_install-devel
00022 p5-Unicode-String-2.09 /converters/p5-Unicode-String
00021 p5-Storable-2.15 /devel/p5-Storable
00020 gpa-0.7.4 /security/gpa
00019 kdeutils-3.5.4 /misc/kdeutils3
00018 gstreamer-0.10.11 /multimedia/gstreamer
00017 xchat-2.6.8_1 /irc/xchat
MGPMrPortBrokeCheck 0.4.1_6 error: gstreamer-plugins-0.10.11,2
/multimedia/gstreamer-plugins marked IGNORE, adding to ignore.db
MGPMrPortBrokeCheck 0.4.1_6 error: gstreamer-plugins-0.10.11,2
/multimedia/gstreamer-plugins marked IGNORE, adding to ignore.db
MGPMrPortBrokeCheck 0.4.1_6 error: gstreamer-plugins-mad-0.10.4_2,2
/audio/gstreamer-plugins-mad marked IGNORE, adding to ignore.db
MGPMrPortBrokeCheck 0.4.1_6 error: gstreamer-plugins-mad-0.10.4_2,2
/audio/gstreamer-plugins-mad marked IGNORE, adding to ignore.db
MGPMrPortBrokeCheck 0.4.1_6 error: gstreamer-plugins-ogg-0.10.11_1,2
/audio/gstreamer-plugins-ogg marked IGNORE, adding to ignore.db
MGPMrPortBrokeCheck 0.4.1_6 error: gstreamer-plugins-ogg-0.10.11_1,2
/audio/gstreamer-plugins-ogg marked IGNORE, adding to ignore.db
MGPMrPortBrokeCheck 0.4.1_6 error: gstreamer-plugins-vorbis-0.10.11_1,2
/audio/gstreamer-plugins-vorbis marked IGNORE, adding to ignore.db
MGPMrPortBrokeCheck 0.4.1_6 error: gstreamer-plugins-vorbis-0.10.11_1,2
/audio/gstreamer-plugins-vorbis marked IGNORE, adding to ignore.db
/usr/ports/audio/gstreamer-plugins-flac/../../multimedia/gstreamer-plugins/Makefile.common,
line 350: Malformed conditional (${gst_${GST_PLUGIN}_GCONF_SCHEMAS}!=)
/usr/ports/audio/gstreamer-plugins-flac/../../multimedia/gstreamer-plugins/Makefile.common,
line 354: Malformed conditional (${gst_${GST_PLUGIN}_USE_SDL}!=)
/usr/ports/audio/gstreamer-plugins-flac/../../multimedia/gstreamer-plugins/Makefile.common,
line 356: if-less endif
/usr/ports/audio/gstreamer-plugins-flac/../../multimedia/gstreamer-plugins/Makefile.common,
line 356: Need an operator
/usr/ports/audio/gstreamer-plugins-flac/../../multimedia/gstreamer-plugins/Makefile.common,
line 377: if-less endif
/usr/ports/audio/gstreamer-plugins-flac/../../multimedia/gstreamer-plugins/Makefile.common,
line 377: Need an operator
make: fatal errors encountered -- cannot continue
MGdbAdd error: attempt to place null data into record halted
assertion 0 failed: file MGdbAdd.c, line 78
Abort trap (core dumped)
([EMAIL PROTECTED])#
What's the best way to resolve this???
Thanks.
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
[Fwd: Re: FreeBSD 5.5 port vlc-devel core dump]
On Thu, Nov 30, 2006 at 08:51:33PM +0100, Roger Olofsson wrote: It is I that should say thanks ;^) I have tried using libmap.conf to remap libpthread to lib_r but that had no effect. Vlc reproduces the core dump exactly. I am not sure that creating libmap.conf in /etc and just entering as below has any effect at all. /etc/libmap.conf [/usr/local/bin/vlc] # 'vlc' uses libc_r. libpthread.so.1 libc_r.so.5 libpthread.so libc_r.so [vlc] libpthread.so.1 libc_r.so.5 libpthread.so libc_r.so Yet again, I am most grateful for your patience and input. If those are the right library revisions then it should work...but I don't see an effect from changing thread libraries either. Kris file:///C|/DOCUME%7E1/RAGGEN/LOKALA%7E1/TEMP/nsmail.tmp Description: PGP signature ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
