RE: arp who-has tcp message not received in my SL6.3 system
Hi , When this issue happens, ping is not working Regards, Arul -Original Message- From: Orion Poplawski [mailto:or...@cora.nwra.com] Sent: Saturday, November 09, 2013 3:54 AM To: Edison, Arul (GE Healthcare); scientific-linux-users@fnal.gov Subject: Re: arp who-has tcp message not received in my SL6.3 system On 11/07/2013 12:13 AM, Edison, Arul (GE Healthcare) wrote: Hi Everyone, I port my application to SL6.3 My SL6.3 PC is connected with another device over Ethernet cable. With the application ported on SL6.3, the device is not able to communicate with my application When I compare the tcpdata exchanged between my PC and device, The below message , that is sent first from the device to my PC is not seen at my SL6.3 PC now. I have checked the rpms installed in my system. rarpd rpm is not installed 11:53:36.359556 arp who-has 192.168.2.30 tell 192.168.2.1 0x: 0001 0800 0604 0001 000b ab2b 595a c0a8 ...+YZ.. 0x0010: 0201 c0a8 021e 11:53:36.359604 arp who-has 192.168.2.30 tell 192.168.2.1 0x: 0001 0800 0604 0001 000b ab2b 595a c0a8 ...+YZ.. 0x0010: 0201 c0a8 021e 11:53:36.359645 arp who-has 192.168.2.30 tell 192.168.2.1 0x: 0001 0800 0604 0001 000b ab2b 595a c0a8 ...+YZ.. 0x0010: 0201 c0a8 021e I would appreciate suggestions on how to make my SL6.3 PC receive arp who-has message Regards, Arul You have some pretty basic connectivity issues between the two machines. Can you ping each other? Are the netmasks correct? -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 http://www.nwra.com
arp who-has message not received in my SL6.3 system
Hi Everyone, I port my application to SL6.3 My SL6.3 PC is connected with another device over Ethernet cable. With the application ported on SL6.3, the device is not able to communicate with my application When I compare the tcpdata exchanged between my PC and device, The below message , that is sent first from the device to my PC is not seen at my SL6.3 PC now. 11:53:36.359556 arp who-has 192.168.2.30 tell 192.168.2.1 0x: 0001 0800 0604 0001 000b ab2b 595a c0a8 ...+YZ.. 0x0010: 0201 c0a8 021e 11:53:36.359604 arp who-has 192.168.2.30 tell 192.168.2.1 0x: 0001 0800 0604 0001 000b ab2b 595a c0a8 ...+YZ.. 0x0010: 0201 c0a8 021e 11:53:36.359645 arp who-has 192.168.2.30 tell 192.168.2.1 0x: 0001 0800 0604 0001 000b ab2b 595a c0a8 ...+YZ.. 0x0010: 0201 c0a8 021e I would appreciate suggestions on how to make my SL6.3 PC receive arp who-has message Regards, Arul
arp who-has tcp message not received in my SL6.3 system
Hi Everyone, I port my application to SL6.3 My SL6.3 PC is connected with another device over Ethernet cable. With the application ported on SL6.3, the device is not able to communicate with my application When I compare the tcpdata exchanged between my PC and device, The below message , that is sent first from the device to my PC is not seen at my SL6.3 PC now. I have checked the rpms installed in my system. rarpd rpm is not installed 11:53:36.359556 arp who-has 192.168.2.30 tell 192.168.2.1 0x: 0001 0800 0604 0001 000b ab2b 595a c0a8 ...+YZ.. 0x0010: 0201 c0a8 021e 11:53:36.359604 arp who-has 192.168.2.30 tell 192.168.2.1 0x: 0001 0800 0604 0001 000b ab2b 595a c0a8 ...+YZ.. 0x0010: 0201 c0a8 021e 11:53:36.359645 arp who-has 192.168.2.30 tell 192.168.2.1 0x: 0001 0800 0604 0001 000b ab2b 595a c0a8 ...+YZ.. 0x0010: 0201 c0a8 021e I would appreciate suggestions on how to make my SL6.3 PC receive arp who-has message Regards, Arul
how to disable boot time check on last mount time
Hi, When install the SL 6.3 I did not configure the system time correctly. It took some default time as Oct 9 17:15:27 2025. After the OS is installed, I set the date to current date. When I reboot the system, boot is halted with error as below Checking filesystems /dev/sda3: Superblock last mount time ( Thu Oct 9 17:15:27 2025,now Wed Oct 30 19:02:49 2013) is in future /dev/sda3: UNEXPECTED INCONSISTENCY;Run fsck MANUALLY Can someone let me know how to disable this check during OS boot? Regards, Arul
issue in CD not ejecting at the end of OS installation
HI, I am porting my application from Redhat to Scientific Linux 6.3 In Scientific Linux the CD is not ejecting at the end of installation though I have added eject at the end of my kick start file. Can someone point how to fix this issue Thanks, Arul
RE: issue in CD not ejecting at the end of OS installation
Hi All, In the kick start file, I have mentioned eject at post section at the end. Still installation DVD is not ejecting . suggestion on what needs to be configured is welcome #platform=x86, AMD64, or Intel EM64T #version=DEVEL # Firewall configuration firewall --disabled install cdrom graphical firstboot --disable keyboard us lang en_US selinux --disabled logging --level=info . %packages %post eject %end -Original Message- From: owner-scientific-linux-us...@listserv.fnal.gov [mailto:owner-scientific-linux-us...@listserv.fnal.gov] On Behalf Of Edison, Arul (GE Healthcare) Sent: Monday, October 21, 2013 3:54 PM To: scientific-linux-users@fnal.gov Subject: issue in CD not ejecting at the end of OS installation HI, I am porting my application from Redhat to Scientific Linux 6.3 In Scientific Linux the CD is not ejecting at the end of installation though I have added eject at the end of my kick start file. Can someone point how to fix this issue Thanks, Arul
how to change the CD mount point
HI, I am porting my application from Redhat to Scientific Linux 6.3 In Scientific Linux, the CD is mounted to mount point /media/CDROM_ I would like to change the mount point location to /mnt/cdrom Any idea what is the configuration to change this? Thanks, Arul
Is there any reason why Kudzu rpm is not part of SL
Hi All, I am trying to use the SL for my application environment and using SL for the same When I install SL , I have found that Kudzuis not part of the SL Is there any reason why this is removed in SL? Regards, Arul
RE: UDP message not recevied at port 8100 with Scientific Linux 6.3
Hi, The Version of the OS that I use is 6.3 The version of the libtirpc package that I have is libtirpc-0.2.1-5.el6.x86_64 The firewall setting that I have is empty [ checked with iptables –L command is as below] Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination Is there anything else that has to be looked in ? Thanks, Arul From: Paul Robert Marino [mailto:prmari...@gmail.com] Sent: Monday, August 19, 2013 2:32 AM To: Edison, Arul (GE Healthcare); Scientific Linux; S, Akshata (GE Healthcare); Rao, Keshava N (GE Healthcare) Subject: Re: UDP message not recevied at port 8100 with Scientific Linux 6.3 -- Sent from my HP Pre3 On Aug 16, 2013 14:36, Konstantin Olchanski olcha...@triumf.camailto:olcha...@triumf.ca wrote: On Fri, Aug 16, 2013 at 11:24:36AM -0700, Konstantin Olchanski wrote: On Fri, Aug 16, 2013 at 02:01:20PM +, Edison, Arul (GE Healthcare) wrote: Hi all, The application that I run on Scientific Linux 6.3 is to receive the UDP message at port 8100. However I found that port 8100 is used by xprint-server Is there a way to disable the xprint-server ? You can use lsof to find out who is consuming UDP packets sent to port 8100. FYI in most cases netstat is a lot easier to get this info example netstat -lunp And add a -t if you want to see TCP as well. (Also check that your packets are not rejected by your own firewall, iptables -L -v). Also SL 6.3 shipped with a defective libtirpc which discards UDP broadcast packets. The bug makes NIS not work. May bite you, too. SL 6.2 or 6.1 was okey, I think, SL 6.4 not sure. I have posted this bug on this mailing list and on RH bugzilla, it is fixed in errata packages. -- Konstantin Olchanski Data Acquisition Systems: The Bytes Must Flow! Email: olchansk-at-triumf-dot-ca Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada
RE: UDP message not recevied at port 8100 with Scientific Linux 6.3
Hi Konstantin Olchanski, Can you provide some more info on how to disable / configure portmap? Below is the rpcbind rpm that is in the system rpcbind-0.2.0-9.el6.x86_64 Thanks, Arul -Original Message- From: Konstantin Olchanski [mailto:olcha...@triumf.ca] Sent: Friday, August 16, 2013 11:55 PM To: Edison, Arul (GE Healthcare) Cc: Scientific Linux; S, Akshata (GE Healthcare); Rao, Keshava N (GE Healthcare) Subject: Re: UDP message not recevied at port 8100 with Scientific Linux 6.3 On Fri, Aug 16, 2013 at 02:01:20PM +, Edison, Arul (GE Healthcare) wrote: Hi all, The application that I run on Scientific Linux 6.3 is to receive the UDP message at port 8100. However I found that port 8100 is used by xprint-server Is there a way to disable the xprint-server? You can use lsof to find out who is consuming UDP packets sent to port 8100. Note that UDP port collisions is a problem because portmap (rpcbind) assigns UDP ports to various daemons kind of randomly and it will eventually collide with any UDP port you decide to chose. One way to avoid this is by using portmap yourself in your application. (Also check that your packets are not rejected by your own firewall, iptables -L -v). -- Konstantin Olchanski Data Acquisition Systems: The Bytes Must Flow! Email: olchansk-at-triumf-dot-ca Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada
RE: network port issue with Scientific Linux 6.3
Thanks. As suggested, I have disabled the NetworkManager and the issue that I faced is solved now -Original Message- From: owner-scientific-linux-us...@listserv.fnal.gov [mailto:owner-scientific-linux-us...@listserv.fnal.gov] On Behalf Of Mark Stodola Sent: Wednesday, August 14, 2013 6:54 PM To: Scientific Linux Subject: Re: network port issue with Scientific Linux 6.3 On 08/14/2013 08:16 AM, Edison, Arul (GE Healthcare) wrote: Hi , I am using the repacked version of Scientific Linux 6.3 My PC has a mother board , which has 2 Ethernet port eth0 is connected to a device IP configured for eth0 is 192.168.2.1 eth1 is connected to a hub. This is intern connected with another PC. IP configured for eth0 is 192.168.1.20 The issue here is eth0 IP Address is now got changed to the IP address of eth1 when the Device connected with eth0 become powered on . With this, eth0 eth1 has same IP address. Because of this the application running on Scientific Linux 6.3 PC is not able to communicate with the Device connected with eth0. I have enclosed the /var/log/message file below for the reference Please suggest me what is the configuration to be done for the same? /etc/sysconfig/network-scripts/ifcfg-eth0 file from system is as below:- *** DEVICE=eth0 ONBOOT=yes BOOTPROTO=none IPADDR=192.168.2.1 NETMASK=255.255.255.0 /etc/sysconfig/network-scripts/ ifcfg-eth1 file from system is as below:- * DEVICE=eth1 BOOTPROTO=none #IPADDR=192.168.1.90 IPADDR=192.168.1.20 NETMASK=255.255.255.0 When the Scientific Linux 6.3 Pc is booted , the network configuration of the system is as below:- eth0 Link encap:Ethernet HWaddr 00:0B:AB:38:29:A6 inet addr:192.168.2.1 Bcast:192.168.2.255 Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:16 Memory:fdbc-fdbe eth1 Link encap:Ethernet HWaddr 00:0B:AB:38:29:A7 inet addr:192.168.1.20 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::20b:abff:fe38:29a7/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:381 errors:0 dropped:0 overruns:0 frame:0 TX packets:267 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:26234 (25.6 KiB) TX bytes:29696 (29.0 KiB) Interrupt:17 Memory:fddc-fdde lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:4 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:240 (240.0 b) TX bytes:240 (240.0 b) When the Device that is connected to the eth0 is powered on and booted, the network configuration of the system changed as below:- * eth0 Link encap:Ethernet HWaddr 00:0B:AB:38:29:A6 inet addr:192.168.1.20 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::20b:abff:fe38:29a6/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4 errors:0 dropped:0 overruns:0 frame:0 TX packets:38 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:240 (240.0 b) TX bytes:9814 (9.5 KiB) Interrupt:16 Memory:fdbc-fdbe eth1 Link encap:Ethernet HWaddr 00:0B:AB:38:29:A7 inet addr:192.168.1.20 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::20b:abff:fe38:29a7/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:6077 errors:0 dropped:0 overruns:0 frame:0 TX packets:4412 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:427716 (417.6 KiB) TX bytes:287127 (280.3 KiB) Interrupt:17 Memory:fddc-fdde lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:42683 errors:0 dropped:0 overruns:0 frame:0 TX packets:42683 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:4447027 (4.2 MiB) TX bytes:4447027 (4.2 MiB) /var/log/message file is as below:- ** Aug 17 11:54:42 magic kernel: ttyS2: LSR safety check engaged! Aug 17 11:54:46 magic kernel: ttyS2: LSR safety check engaged! Aug 17 11:54:57 magic kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None Aug 17 11:54:57 magic kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Aug 17 11:54:57 magic NetworkManager[1612]: info (eth0): carrier now ON (device state 2) Aug 17 11:54:57 magic NetworkManager[1612]: info (eth0): device state change: 2 - 3 (reason 40) Aug 17 11:54:57 magic NetworkManager[1612]: info
network port issue with Scientific Linux 6.3
Hi , I am using the repacked version of Scientific Linux 6.3 My PC has a mother board , which has 2 Ethernet port eth0 is connected to a device IP configured for eth0 is 192.168.2.1 eth1 is connected to a hub. This is intern connected with another PC. IP configured for eth0 is 192.168.1.20 The issue here is eth0 IP Address is now got changed to the IP address of eth1 when the Device connected with eth0 become powered on . With this, eth0 eth1 has same IP address. Because of this the application running on Scientific Linux 6.3 PC is not able to communicate with the Device connected with eth0. I have enclosed the /var/log/message file below for the reference Please suggest me what is the configuration to be done for the same? /etc/sysconfig/network-scripts/ifcfg-eth0 file from system is as below:- *** DEVICE=eth0 ONBOOT=yes BOOTPROTO=none IPADDR=192.168.2.1 NETMASK=255.255.255.0 /etc/sysconfig/network-scripts/ ifcfg-eth1 file from system is as below:- * DEVICE=eth1 BOOTPROTO=none #IPADDR=192.168.1.90 IPADDR=192.168.1.20 NETMASK=255.255.255.0 When the Scientific Linux 6.3 Pc is booted , the network configuration of the system is as below:- eth0 Link encap:Ethernet HWaddr 00:0B:AB:38:29:A6 inet addr:192.168.2.1 Bcast:192.168.2.255 Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:16 Memory:fdbc-fdbe eth1 Link encap:Ethernet HWaddr 00:0B:AB:38:29:A7 inet addr:192.168.1.20 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::20b:abff:fe38:29a7/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:381 errors:0 dropped:0 overruns:0 frame:0 TX packets:267 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:26234 (25.6 KiB) TX bytes:29696 (29.0 KiB) Interrupt:17 Memory:fddc-fdde loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:4 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:240 (240.0 b) TX bytes:240 (240.0 b) When the Device that is connected to the eth0 is powered on and booted, the network configuration of the system changed as below:- * eth0 Link encap:Ethernet HWaddr 00:0B:AB:38:29:A6 inet addr:192.168.1.20 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::20b:abff:fe38:29a6/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4 errors:0 dropped:0 overruns:0 frame:0 TX packets:38 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:240 (240.0 b) TX bytes:9814 (9.5 KiB) Interrupt:16 Memory:fdbc-fdbe eth1 Link encap:Ethernet HWaddr 00:0B:AB:38:29:A7 inet addr:192.168.1.20 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::20b:abff:fe38:29a7/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:6077 errors:0 dropped:0 overruns:0 frame:0 TX packets:4412 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:427716 (417.6 KiB) TX bytes:287127 (280.3 KiB) Interrupt:17 Memory:fddc-fdde loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:42683 errors:0 dropped:0 overruns:0 frame:0 TX packets:42683 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:4447027 (4.2 MiB) TX bytes:4447027 (4.2 MiB) /var/log/message file is as below:- ** Aug 17 11:54:42 magic kernel: ttyS2: LSR safety check engaged! Aug 17 11:54:46 magic kernel: ttyS2: LSR safety check engaged! Aug 17 11:54:57 magic kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None Aug 17 11:54:57 magic kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Aug 17 11:54:57 magic NetworkManager[1612]: info (eth0): carrier now ON (device state 2) Aug 17 11:54:57 magic NetworkManager[1612]: info (eth0): device state change: 2 - 3 (reason 40) Aug 17 11:54:57 magic NetworkManager[1612]: info Activation (eth0) starting connection 'eth1' Aug 17 11:54:57 magic NetworkManager[1612]: info (eth0):
