Re: portupgrade coredumps
Am 29.9.2007 22:55 Uhr, Ihsan Dogan schrieb: [EMAIL PROTECTED]:~# portupgrade -a [Updating the pkgdb format:dbm_hash in /var/db/pkg ... - 655 packages found (-2 +1) (...)/usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:429: [BUG] Segmentation fault ruby 1.8.6 (2007-03-13) [i386-freebsd6] Abort trap: 6 (core dumped) I have installed portupgrade-devel and it works now. Ihsan -- [EMAIL PROTECTED] http://blog.dogan.ch/ http://ihsan.dogan.ch/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
portupgrade coredumps
Hello, Recently, I've run into this problem: -- [EMAIL PROTECTED]:~# portupgrade -a [Updating the pkgdb format:dbm_hash in /var/db/pkg ... - 655 packages found (-2 +1) (...)/usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:429: [BUG] Segmentation fault ruby 1.8.6 (2007-03-13) [i386-freebsd6] Abort trap: 6 (core dumped) -- (gdb) bt #0 0x28260613 in kill () from /lib/libc.so.6 #1 0x28178447 in raise () from /lib/libpthread.so.2 #2 0x2825f1e8 in abort () from /lib/libc.so.6 #3 0x28099d74 in rb_bug () from /usr/local/lib/libruby18.so.18 #4 0x2811991b in ruby_digitmap () from /usr/local/lib/libruby18.so.18 #5 0x28131d41 in ruby_release_date () from /usr/local/lib/libruby18.so.18 #6 0x28131d36 in ruby_platform () from /usr/local/lib/libruby18.so.18 #7 0x28131d28 in ruby_patchlevel () from /usr/local/lib/libruby18.so.18 #8 0xbfbf1980 in ?? () #9 0x in ?? () #10 0x in ?? () #11 0x0002 in ?? () #12 0x in ?? () #13 0x280a6832 in rb_call0 () from /usr/local/lib/libruby18.so.18 Previous frame inner to this frame (corrupt stack?) -- [EMAIL PROTECTED]:~# pkg_info | grep ruby ruby-1.8.6_2,1 An object-oriented interpreted scripting language [EMAIL PROTECTED]:~# pkg_info | grep portupgrade portupgrade-2.3.1,2 FreeBSD ports/packages administration and management tool s -- What's going wrong here? Ihsan -- [EMAIL PROTECTED] http://blog.dogan.ch/ http://ihsan.dogan.ch/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
NFS file locking problems on 6.1
Hello, I'm running an NFS server and a client on 6.1. On the client the the /home is mounted through /etc/fstab from the nfs server. rc.conf on the server: rpcbind_enable=YES# Run the portmapper service (YES/NO). mountd_enable=YES # Run mountd (or NO). nfs_server_enable=YES # This host is an NFS server (or NO). nfs_server_flags=-u -t -n 8 # Flags to nfsd (if enabled). nfs_client_enable=YES # This host is an NFS client (or NO). rpc_lockd_enable=YES # Run NFS rpc.lockd needed for client/server. rpc_statd_enable=YES # Run NFS rpc.statd needed for client/server. rc.conf on the client: nfs_client_enable=YES # This host is an NFS client (or NO). rpcbind_enable=YES# Run the portmapper service (YES/NO). rpc_lockd_enable=YES # Run NFS rpc.lockd needed for client/server. rpc_statd_enable=YES # Run NFS rpc.statd needed for client/server. fstab on the client: defiant.lan.dogan.ch:/export/storage0/home /home nfs noinet6,tcp,rw 0 0 My problem is, that after a reboot of the client the file locking is working fine. When the applications are starting to lock files, it's impossible to lock files from the client anymore. I'm wondering now if I have a configuration mistake or a if I'm running into a bug. Ihsan -- [EMAIL PROTECTED] http://ihsan.dogan.ch/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhcrelay is setting the relay ip address wrong
On Wednesday, 07 Sep 2005 16:27 +0200, Ihsan Dogan wrote:
The relay agent is acting exactly the way it should. When it gets a
DHCP request in from a client, it uses its own address ON THE CLIENT'S
NETWORK for the relay agent address. This way, the DHCP server can
tell which network the client is on, and thus which set of addresses
to use for assigning an address to the client.
What is the problem?
Perhaps I've sent this e-mail too early. I did some further
investigation and saw that:
select(7,{4 5 6},{},{},0x0) = 2 (0x2)
gettimeofday({1126033610 52754},0x0) = 0 (0x0)
read(0x6,0x806e000,0x1000) = 360 (0x168)
sendto(0x4,0xbfbfd950,0,0x0,{ AF_INET 213.144.141.146:67 },0x10) = 300 (0x12c)
write(2,0x8066cc0,62)= 62 (0x3e)
write(2,0x80620b8,1) = 1 (0x1)
recvfrom(0x4,0xbfbfe3a0,0,0x0,{ AF_INET 0.0.0.0:68 },0xbfbfe38c) = 300 (0x12c)
select(7,{4 5 6},{},{},0x0) = 1 (0x1)
gettimeofday({1126033610 72933},0x0) = 0 (0x0)
recvfrom(0x4,0xbfbfe3a0,0,0x0,{ AF_INET 213.144.141.146:67 },0xbfbfe38c) =
300 (0x12c)
The dhcrelay is forwarding the request from the client correctly
to the server, but it does not forward the reply from the server
to the client.
I've asked also on the ISC's dhcp server list and this is the
answer I've got:
No, input from this socket is dropped.
See 'fallback_discard' in common/socket.c.
You're railing against a very commonly reported problem. The IO system
was designed for the server and client (mostly for the server). It is
poorly suited to the relay.
Enhancements are on the wishlist for 3.1.
Ihsan...
--
[EMAIL PROTECTED] http://ihsan.dogan.ch/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhcrelay is setting the relay ip address wrong
On Wednesday, 07 Sep 2005 10:06 -0400, Lowell Gilbert wrote:
Did I something wrong? A bug?
The relay agent is acting exactly the way it should. When it gets a
DHCP request in from a client, it uses its own address ON THE CLIENT'S
NETWORK for the relay agent address. This way, the DHCP server can
tell which network the client is on, and thus which set of addresses
to use for assigning an address to the client.
What is the problem?
Perhaps I've sent this e-mail too early. I did some further
investigation and saw that:
select(7,{4 5 6},{},{},0x0) = 2 (0x2)
gettimeofday({1126033610 52754},0x0) = 0 (0x0)
read(0x6,0x806e000,0x1000) = 360 (0x168)
sendto(0x4,0xbfbfd950,0,0x0,{ AF_INET 213.144.141.146:67 },0x10) = 300 (0x12c)
write(2,0x8066cc0,62)= 62 (0x3e)
write(2,0x80620b8,1) = 1 (0x1)
recvfrom(0x4,0xbfbfe3a0,0,0x0,{ AF_INET 0.0.0.0:68 },0xbfbfe38c) = 300 (0x12c)
select(7,{4 5 6},{},{},0x0) = 1 (0x1)
gettimeofday({1126033610 72933},0x0) = 0 (0x0)
recvfrom(0x4,0xbfbfe3a0,0,0x0,{ AF_INET 213.144.141.146:67 },0xbfbfe38c) = 300
(0x12c)
The dhcrelay is forwarding the request from the client correctly
to the server, but it does not forward the reply from the server
to the client.
Ihsan
--
[EMAIL PROTECTED] http://ihsan.dogan.ch/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
dhcrelay is setting the relay ip address wrong
Hello, I'm running a small router/firewall on a FreeBSD 5.4 system. This machine should also act as a DHCP gateway. For the dhcp relay, I'm using ISC's dhcrelay (from Ports isc-dhcp3-relay-3.0.3). The Interfaca and network configuration: hme0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=bRXCSUM,TXCSUM,VLAN_MTU inet 213.144.141.145 netmask 0xfff8 broadcast 213.144.141.151 inet6 fe80::a00:20ff:feb4:42cc%hme0 prefixlen 64 scopeid 0x1 inet6 2001:470:1f01:569::1 prefixlen 112 ether 08:00:20:b4:42:cc media: Ethernet autoselect (100baseTX full-duplex) status: active hme1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=bRXCSUM,TXCSUM,VLAN_MTU inet 192.168.23.1 netmask 0xff00 broadcast 192.168.23.255 inet6 fe80::a00:20ff:feb4:42cd%hme1 prefixlen 64 scopeid 0x2 ether 08:00:20:b4:42:cd media: Ethernet autoselect (100baseTX full-duplex) status: active hme2: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=bRXCSUM,TXCSUM,VLAN_MTU inet 192.168.42.1 netmask 0xff00 broadcast 192.168.42.255 inet6 fe80::a00:20ff:feb4:42ce%hme2 prefixlen 64 scopeid 0x3 ether 08:00:20:b4:42:ce media: Ethernet autoselect (100baseTX full-duplex) status: active The DHCP server is on the subnet of hme0; the DHCP clients are on hme1 on hme2. netstat -rnf inet: DestinationGatewayFlagsRefs Use Netif Expire default213.144.128.205UGS 0 250630 tun0 127.0.0.1 127.0.0.1 UH 0 71lo0 192.168.23 link#2 UC 00 hme1 192.168.23.2 00:c0:49:5a:1d:ca UHLW02 hme1823 192.168.42 link#3 UC 00 hme2 213.144.128.205213.144.146.12 UH 10 tun0 213.144.141.144ff:ff:ff:ff:ff:ff UHLWb 03 hme0 = 213.144.141.144/29 link#1 UC 00 hme0 213.144.141.14600:08:c7:3a:df:a9 UHLW0 104123 hme0233 213.144.141.14700:07:e9:14:1a:a1 UHLW038011 hme0322 213.144.141.151ff:ff:ff:ff:ff:ff UHLWb 01 hme0 The dhcrelay is started with the following options: /usr/local/sbin/dhcrelay -i hme1 -i hme2 -d -a 213.144.141.146 The dhcrelay receives the request and passes them to the DHCP server, but the forwarded package contains the relay agent ip address of 192.168.23.1 and not 213.144.141.145 how it should be. In that case, the DHCP server is sending the reply to 192.168.23.1 and not to 213.144.141.145. Did I something wrong? A bug? Ihsan -- [EMAIL PROTECTED] http://ihsan.dogan.ch/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: browsing networks
On Saturday, 25 Oct 2003 02:38, Joe Marcus Clarke wrote: Install devel/gnomevfs-extras, then enter smb:/// as the location. You should see all your servers. I something similar available for nfs? Ihsan... -- Swiss Unix User Group: http://www.suug.ch/ Software Packages for Solaris: http://www.blastwave.org/ pgp0.pgp Description: PGP signature
