Unable to ssh nodes with global IP
Dear List, My internet connection is via mobile broadband. The ifconfig lists the ppp0 with IP address, ppp0 Link encap:Point-to-Point Protocol inet addr:120.165.xx.xxx P-t-P:10.64.64.64 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:5239 errors:0 dropped:0 overruns:0 frame:0 TX packets:6371 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:3867747 (3.6 MiB) TX bytes:1020544 (996.6 KiB) I tried to remote login (using ssh) to this IP address from another machine but failed. The following message appears, ssh: connect to host 120.166.xx.xxx port 22: Connection timed out Editing /etc/sysconfig/iptables and add --dport 22 -j Accept does not help. Could any one please provide some suggestions? Thanks in advance, AA -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Unable to ssh nodes with global IP
On Sat, Oct 22, 2011 at 11:31 AM, Abu Attar Musharih wrote: > I tried to remote login (using ssh) to this IP address from another > machine but failed. > > The following message appears, > > ssh: connect to host 120.166.xx.xxx port 22: Connection timed out > > > Editing /etc/sysconfig/iptables and add --dport 22 -j Accept does not help. > > Could any one please provide some suggestions? > Are you certain that your provider allows such connections? You could ask their customer support if they know. -- Suvayu Open source is the future. It sets us free. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Unable to ssh nodes with global IP
2011/10/22, Abu Attar Musharih : > Dear List, > > My internet connection is via mobile broadband. The ifconfig lists > the ppp0 with IP address, > > > ppp0 Link encap:Point-to-Point Protocol > inet addr:120.165.xx.xxx P-t-P:10.64.64.64 Mask:255.255.255.255 > UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 > RX packets:5239 errors:0 dropped:0 overruns:0 frame:0 > TX packets:6371 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:3 > RX bytes:3867747 (3.6 MiB) TX bytes:1020544 (996.6 KiB) > > I tried to remote login (using ssh) to this IP address from another > machine but failed. > > The following message appears, > > ssh: connect to host 120.166.xx.xxx port 22: Connection timed out > > > Editing /etc/sysconfig/iptables and add --dport 22 -j Accept does not help. > > Could any one please provide some suggestions? Can you ping the machine? If yes, then are there traces in the logs that show the connection attempts? (You can make iptables log those.) I don't know much about networking, but I think it's good to isolate where the real problem lies. It may not have to do anything with ssh or the firewall. Andras -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Unable to ssh nodes with global IP
Hi, Could be several reasons. I presume that you succeede in ssh-ing to that machine, from another client (i.e. The machine does accept incomoing ssh-request) Perhaps firewall settings? Or accept/deny configurations? - Oorspronkelijk bericht - Van: Abu Attar Musharih [mailto:abuattar.musha...@gmail.com] Verzonden: Saturday, October 22, 2011 11:31 AM Aan: Community support for Fedora users Onderwerp: Unable to ssh nodes with global IP Dear List, My internet connection is via mobile broadband. The ifconfig lists the ppp0 with IP address, ppp0 Link encap:Point-to-Point Protocol inet addr:120.165.xx.xxx P-t-P:10.64.64.64 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:5239 errors:0 dropped:0 overruns:0 frame:0 TX packets:6371 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:3867747 (3.6 MiB) TX bytes:1020544 (996.6 KiB) I tried to remote login (using ssh) to this IP address from another machine but failed. The following message appears, ssh: connect to host 120.166.xx.xxx port 22: Connection timed out Editing /etc/sysconfig/iptables and add --dport 22 -j Accept does not help. Could any one please provide some suggestions? Thanks in advance, AA -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines __ Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het elektronisch verzenden van berichten. This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The State accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Unable to ssh nodes with global IP
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/22/2011 04:31 AM, Abu Attar Musharih wrote: > Dear List, > > My internet connection is via mobile broadband. The ifconfig lists > the ppp0 with IP address, > > > ppp0 Link encap:Point-to-Point Protocol > inet addr:120.165.xx.xxx P-t-P:10.64.64.64 Mask:255.255.255.255 > UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 > RX packets:5239 errors:0 dropped:0 overruns:0 frame:0 > TX packets:6371 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:3 > RX bytes:3867747 (3.6 MiB) TX bytes:1020544 (996.6 KiB) > > I tried to remote login (using ssh) to this IP address from another > machine but failed. > > The following message appears, > > ssh: connect to host 120.166.xx.xxx port 22: Connection timed out > > > Editing /etc/sysconfig/iptables and add --dport 22 -j Accept does not help. > > Could any one please provide some suggestions? > > Thanks in advance, > AA Dumb question 1: Did you reload iptables after making the changes? Dumb question 2: Is sshd running on the machine you are trying to connect to? Mikkel - -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup! -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk6itEQACgkQqbQrVW3JyMSQwgCfdxzWs5vbObesZubgShCS6ORe aRUAn2ysuiqsHmguRL7G/+JxmnxsWkDS =AZ9V -END PGP SIGNATURE- -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Unable to ssh nodes with global IP
On 10/22/2011 08:17 PM, Mikkel L. Ellertson wrote: > On 10/22/2011 04:31 AM, Abu Attar Musharih wrote: > > Dear List, > > > My internet connection is via mobile broadband. The ifconfig lists > > the ppp0 with IP address, > > > > ppp0 Link encap:Point-to-Point Protocol > > inet addr:120.165.xx.xxx P-t-P:10.64.64.64 > Mask:255.255.255.255 > > UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 > > RX packets:5239 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:6371 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:3 > > RX bytes:3867747 (3.6 MiB) TX bytes:1020544 (996.6 KiB) > > > I tried to remote login (using ssh) to this IP address from another > > machine but failed. > > > The following message appears, > > > ssh: connect to host 120.166.xx.xxx port 22: Connection timed out > > > > Editing /etc/sysconfig/iptables and add --dport 22 -j Accept does > not help. > > > Could any one please provide some suggestions? > > > Thanks in advance, > > AA > Dumb question 1: Did you reload iptables after making the changes? > > Dumb question 2: Is sshd running on the machine you are trying to > connect to? > > Dumb question 3: Above one sees... inet addr:120.165.xx.xxx And then one sees... ssh: connect to host 120.166.xx.xxx Does anyone see a difference between 165 and 166? -- Even if you do learn to speak correct English, whom are you going to speak it to? -- Clarence Darrow -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Unable to ssh nodes with global IP
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/22/2011 07:28 AM, Ed Greshko wrote: > On 10/22/2011 08:17 PM, Mikkel L. Ellertson wrote: >> On 10/22/2011 04:31 AM, Abu Attar Musharih wrote: >>> Dear List, >> >>> My internet connection is via mobile broadband. The ifconfig lists >>> the ppp0 with IP address, >> >> >>> ppp0 Link encap:Point-to-Point Protocol >>> inet addr:120.165.xx.xxx P-t-P:10.64.64.64 >> Mask:255.255.255.255 >>> UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 >>> RX packets:5239 errors:0 dropped:0 overruns:0 frame:0 >>> TX packets:6371 errors:0 dropped:0 overruns:0 carrier:0 >>> collisions:0 txqueuelen:3 >>> RX bytes:3867747 (3.6 MiB) TX bytes:1020544 (996.6 KiB) >> >>> I tried to remote login (using ssh) to this IP address from another >>> machine but failed. >> >>> The following message appears, >> >>> ssh: connect to host 120.166.xx.xxx port 22: Connection timed out >> >> >>> Editing /etc/sysconfig/iptables and add --dport 22 -j Accept does >> not help. >> >>> Could any one please provide some suggestions? >> >>> Thanks in advance, >>> AA >> Dumb question 1: Did you reload iptables after making the changes? >> >> Dumb question 2: Is sshd running on the machine you are trying to >> connect to? >> >> > > Dumb question 3: Above one sees... inet addr:120.165.xx.xxx > > And then one sees... ssh: connect to host 120.166.xx.xxx > > Does anyone see a difference between 165 and 166? > I missed that - I think you nailed it. (Time for coffee!) Mikkel - -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup! -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk6iu5wACgkQqbQrVW3JyMSz9ACfSxeK7LTkJ5oan/VPszLrZGgL obYAn2yhKDuuzyywU4tKYGokd5HRjhGw =sCsS -END PGP SIGNATURE- -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Openfoam
Ok, I'm pretty much giving up. This is some strange software from a build/install point of view. The build takes forever, bundles a lot of projects... If anyone is interested in the source RPM I started let me know. An easier option may be FreeFOAM. It's a fork of OpenFOAM that uses cmake. It's only in release candidate but should be much easier to package. http://freefoam.sourceforge.net/index.html Richard -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Cannot configure printer that is on a windows server
The issue isn't ip address vs name either one works. The issue is why am I being asked for authentication information when none is configured on the windows side? I can access the server via smbclient with no issues, but I can't configure a printer using s-c-p because it asks for authentication. Paolo On Fri, Oct 21, 2011 at 4:01 PM, Mikkel L. Ellertson wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 10/21/2011 04:58 PM, Paolo Galtieri wrote: > > If I run > > > > smbclient -L 192.168.1.110 > > > > I get the following. Note that it doesn't matter what I enter when it > > prompts for root password. > > > > Enter root's password: > > session request to 192.168.1.110 failed (Called name not present) > > Domain=[TALOFA01] OS=[Windows 7 Ultimate 7601 Service Pack 1] > > Server=[Windows 7 Ultimate 6.1] > > > > Sharename Type Comment > > - --- > > > > > > E$ Disk Default share > > Epson Stylus Photo 1270 ESCP 2 Printer Epson Stylus Photo 1270 > ESC/P 2 > > EPSON Stylus Photo RX595 Series Printer EPSON Stylus Photo RX595 > Series > > F$ Disk Default share > > G$ Disk Default share > > > > > > > > Y$ Disk Default share > > Z$ Disk Default share > > session request to 192.168.1.110 failed (Called name not present) > > session request to 192 failed (Called name not present) > > session request to *SMBSERVER failed (Called name not present) > > NetBIOS over TCP disabled -- no workgroup available > > > > I removed some of the output, but it shows the printers I want to > > access, but can't. > > > > Paolo > Dumb question - what happens if you use the Windows name for the > computer, instead of its IP address? I do not know about Windows 7, > but I know XP does not like it when you use the IP address instead > of the computer's name. > > smbclient -L MARY-XP works. > smbclient -L 192.168.55.33 does not, even though they are the same > machine, and I can ping 192.168.55.33. On the other hand, Samba > servers will accept either form. > > Mikkel > - -- > > Do not meddle in the affairs of dragons, > for thou art crunchy and taste good with Ketchup! > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.11 (GNU/Linux) > > iEYEARECAAYFAk6h+bIACgkQqbQrVW3JyMSXGACfTXVRxK/2OQKvISC6dP6+g7iS > /QEAn1l8TjsL8v2S8JqhDiRAZP+9AMyE > =Q6E8 > -END PGP SIGNATURE- > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
NFS issues
I have a small home LAN. I am running FC15 on the server. As I still have not made a full peace with FC15 I'm still running FC13 on the client. Several years and FC versions ago, someone on the list told me about this procedure for setting up NFS, which has been working fine... until now. On the server (192.168.1.14): My /etc/exports file looks like this: /home/magnusg/Music 192.168.1.12,192.168.1.13(rw,insecure,sync,nohide) Using the system-config-nfs "General Options tab" I have "Allow connections from port 1024 and higher" checked. I have services nfs and nfslock running on levels 3,4,5. In /etc/sysconfig/nfs I've set these ports: RQUOTAD_PORT=4000 LOCKD_TCPPORT=4001 LOCKD_UDPPORT=4001 MOUNTD_PORT=4002 STATD_PORT=4003 In the firewall I have these ports open: NFSV4 2049 (tcp) 4000-4003 (tcp and udp) 111 (tcp and udp) on the client (192.168.1.13): I added this to /etc/fstab: 192.168.1.14:/home/magnusg/Music/home/magnusg/Musicnfs rw,auto,hard,intr,bg 0 0 Services netfs, nfslock and rpcbind are running on levels 3,4,5. When I boot the client and get to the "Mounting NFS filesystems" section I don't get error messages -- but I do see this: mount.nfs: backgrounding 192.168.1.14:/home/magnusg/Music : mount options "hard,intr,bg,vers=4,addr=192.168.1.14,clientaddr=192.168.1.13" Then I don't get a "Music" icon on my desktop, and when I open the folder there's nothing in it. Any advice on how to proceed would be appreciated. Jerry -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: NFS issues
On 10/23/2011 07:24 AM, Gerhard Magnus wrote: > I have a small home LAN. I am running FC15 on the server. As I still > have not made a full peace with FC15 I'm still running FC13 on the > client. Several years and FC versions ago, someone on the list told me > about this procedure for setting up NFS, which has been working fine... > until now. You may be running into the same bug others have That is NFS mounts not mounting at boot time. There is a bugzilla open for it https://bugzilla.redhat.com/show_bug.cgi?id=692008 Try mounting manually. If that works, then you're experiencing the bug. > > > > On the server (192.168.1.14): > > My /etc/exports file looks like this: > /home/magnusg/Music > 192.168.1.12,192.168.1.13(rw,insecure,sync,nohide) > > Using the system-config-nfs "General Options tab" I have "Allow > connections from port 1024 and higher" checked. > > I have services nfs and nfslock running on levels 3,4,5. > > In /etc/sysconfig/nfs I've set these ports: > RQUOTAD_PORT=4000 > LOCKD_TCPPORT=4001 > LOCKD_UDPPORT=4001 > MOUNTD_PORT=4002 > STATD_PORT=4003 > > In the firewall I have these ports open: > NFSV4 2049 (tcp) > 4000-4003 (tcp and udp) > 111 (tcp and udp) > > > > on the client (192.168.1.13): > > I added this to /etc/fstab: > 192.168.1.14:/home/magnusg/Music/home/magnusg/Musicnfs > rw,auto,hard,intr,bg 0 0 > > Services netfs, nfslock and rpcbind are running on levels 3,4,5. > > > > When I boot the client and get to the "Mounting NFS filesystems" section > I don't get error messages -- but I do see this: > mount.nfs: backgrounding 192.168.1.14:/home/magnusg/Music > : mount options > "hard,intr,bg,vers=4,addr=192.168.1.14,clientaddr=192.168.1.13" > > Then I don't get a "Music" icon on my desktop, and when I open the > folder there's nothing in it. > > Any advice on how to proceed would be appreciated. > Jerry > > > > > -- Even if you do learn to speak correct English, whom are you going to speak it to? -- Clarence Darrow -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: NFS issues
> On 10/23/2011 07:24 AM, Gerhard Magnus wrote: > > I have a small home LAN. I am running FC15 on the server. As I still > > have not made a full peace with FC15 I'm still running FC13 on the > > client. Several years and FC versions ago, someone on the list told me > > about this procedure for setting up NFS, which has been working fine... > > until now. > > > > > > On the server (192.168.1.14): > > My /etc/exports file looks like this: > > /home/magnusg/Music > > 192.168.1.12,192.168.1.13(rw,insecure,sync,nohide) > > Using the system-config-nfs "General Options tab" I have "Allow > > connections from port 1024 and higher" checked. > > I have services nfs and nfslock running on levels 3,4,5. > > In /etc/sysconfig/nfs I've set these ports: > > RQUOTAD_PORT=4000 > > LOCKD_TCPPORT=4001 > > LOCKD_UDPPORT=4001 > > MOUNTD_PORT=4002 > > STATD_PORT=4003 > > In the firewall I have these ports open: > > NFSV4 2049 (tcp) > > 4000-4003 (tcp and udp) > > 111 (tcp and udp) > > > > on the client (192.168.1.13): > > I added this to /etc/fstab: > > 192.168.1.14:/home/magnusg/Music/home/magnusg/Musicnfs > > rw,auto,hard,intr,bg 0 0 > > Services netfs, nfslock and rpcbind are running on levels 3,4,5. > > > > When I boot the client and get to the "Mounting NFS filesystems" section > > I don't get error messages -- but I do see this: > > mount.nfs: backgrounding 192.168.1.14:/home/magnusg/Music > > : mount options > > "hard,intr,bg,vers=4,addr=192.168.1.14,clientaddr=192.168.1.13" > > Then I don't get a "Music" icon on my desktop, and when I open the > > folder there's nothing in it. On Sun, 2011-10-23 at 07:32 +0800, Ed Greshko wrote > You may be running into the same bug others have That is NFS mounts > not mounting at boot time. There is a bugzilla open for it > https://bugzilla.redhat.com/show_bug.cgi?id=692008 > > Try mounting manually. If that works, then you're experiencing the bug. Is this the right mount command? mount -t nfs 192.168.1.14:/home/magnusg/Music /home/magnusg/Music I get this error message: mount.nfs: Connection timed out -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: NFS issues
Yes, mount command seems fine to me. What does this command say mount -t nfs,_netdev 192.168.1.14:/home/magnusg/Music /home/magnusg/Music --Soham On Sun, Oct 23, 2011 at 5:12 AM, Gerhard Magnus wrote: > > > On 10/23/2011 07:24 AM, Gerhard Magnus wrote: > > > I have a small home LAN. I am running FC15 on the server. As I still > > > have not made a full peace with FC15 I'm still running FC13 on the > > > client. Several years and FC versions ago, someone on the list told me > > > about this procedure for setting up NFS, which has been working fine... > > > until now. > > > > > > > > > > On the server (192.168.1.14): > > > My /etc/exports file looks like this: > > > /home/magnusg/Music > > > 192.168.1.12,192.168.1.13(rw,insecure,sync,nohide) > > > Using the system-config-nfs "General Options tab" I have "Allow > > > connections from port 1024 and higher" checked. > > > I have services nfs and nfslock running on levels 3,4,5. > > > In /etc/sysconfig/nfs I've set these ports: > > > RQUOTAD_PORT=4000 > > > LOCKD_TCPPORT=4001 > > > LOCKD_UDPPORT=4001 > > > MOUNTD_PORT=4002 > > > STATD_PORT=4003 > > > In the firewall I have these ports open: > > > NFSV4 2049 (tcp) > > > 4000-4003 (tcp and udp) > > > 111 (tcp and udp) > > > > > > on the client (192.168.1.13): > > > I added this to /etc/fstab: > > > 192.168.1.14:/home/magnusg/Music/home/magnusg/Musicnfs > > > rw,auto,hard,intr,bg 0 0 > > > Services netfs, nfslock and rpcbind are running on levels 3,4,5. > > > > > > When I boot the client and get to the "Mounting NFS filesystems" > section > > > I don't get error messages -- but I do see this: > > > mount.nfs: backgrounding 192.168.1.14:/home/magnusg/Music > > > : mount options > > > "hard,intr,bg,vers=4,addr=192.168.1.14,clientaddr=192.168.1.13" > > > Then I don't get a "Music" icon on my desktop, and when I open the > > > folder there's nothing in it. > > On Sun, 2011-10-23 at 07:32 +0800, Ed Greshko wrote > > You may be running into the same bug others have That is NFS > mounts > > not mounting at boot time. There is a bugzilla open for it > > https://bugzilla.redhat.com/show_bug.cgi?id=692008 > > > > Try mounting manually. If that works, then you're experiencing the > bug. > > Is this the right mount command? > mount -t nfs 192.168.1.14:/home/magnusg/Music /home/magnusg/Music > > I get this error message: > mount.nfs: Connection timed out > > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Apache2 problem - Ubuntu 11.10
I had noticed over past days that calling web pages from localhost seems to take longer, sometimes around 10-15 seconds or more. I installed django on Friday but it did not work so uninstalled and removed residual files. Now calling localhost or 127.0.0.1 gives blank browser. /var/log/apache2/error.log reports: [Sun Oct 23 10:58:46 2011] [notice] child pid 15731 exit signal Segmentation fault (11) [Sun Oct 23 10:58:46 2011] [notice] child pid 15732 exit signal Segmentation fault (11) [Sun Oct 23 10:58:46 2011] [notice] child pid 15733 exit signal Segmentation fault (11) I can access our server pages and google is ok. No help from google on segmentation fault that I could find. Can anyone advise me why this happens to localhost, what I should be aware of and how to fix please. Thanks in advance Roger -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: NFS issues
On Sun, 2011-10-23 at 05:19 +0530, Soham Chakraborty wrote: > Yes, mount command seems fine to me. What does this command say > > mount -t nfs,_netdev > 192.168.1.14:/home/magnusg/Music /home/magnusg/Music magnusg@PuteB Sat Oct 22 17:03:07 [1004] ~ $ su -c "mount -t nfs,_netdev 192.168.1.14:/home/magnusg/Music /home/magnusg/Music" mount.nfs: Connection timed out > > On Sun, Oct 23, 2011 at 5:12 AM, Gerhard Magnus > wrote: > > > On 10/23/2011 07:24 AM, Gerhard Magnus wrote: > > > I have a small home LAN. I am running FC15 on the server. > As I still > > > have not made a full peace with FC15 I'm still running > FC13 on the > > > client. Several years and FC versions ago, someone on the > list told me > > > about this procedure for setting up NFS, which has been > working fine... > > > until now. > > > > > > > > > > > > On the server (192.168.1.14): > > > My /etc/exports file looks like this: > > > /home/magnusg/Music > > > 192.168.1.12,192.168.1.13(rw,insecure,sync,nohide) > > > Using the system-config-nfs "General Options tab" I have > "Allow > > > connections from port 1024 and higher" checked. > > > I have services nfs and nfslock running on levels 3,4,5. > > > In /etc/sysconfig/nfs I've set these ports: > > > RQUOTAD_PORT=4000 > > > LOCKD_TCPPORT=4001 > > > LOCKD_UDPPORT=4001 > > > MOUNTD_PORT=4002 > > > STATD_PORT=4003 > > > In the firewall I have these ports open: > > > NFSV4 2049 (tcp) > > > 4000-4003 (tcp and udp) > > > 111 (tcp and udp) > > > > > > on the client (192.168.1.13): > > > I added this to /etc/fstab: > > > 192.168.1.14:/home/magnusg/Music/home/magnusg/Music > nfs > > > rw,auto,hard,intr,bg 0 0 > > > Services netfs, nfslock and rpcbind are running on levels > 3,4,5. > > > > > > When I boot the client and get to the "Mounting NFS > filesystems" section > > > I don't get error messages -- but I do see this: > > > mount.nfs: backgrounding 192.168.1.14:/home/magnusg/Music > > > : mount options > > > > "hard,intr,bg,vers=4,addr=192.168.1.14,clientaddr=192.168.1.13" > > > Then I don't get a "Music" icon on my desktop, and when I > open the > > > folder there's nothing in it. > > > On Sun, 2011-10-23 at 07:32 +0800, Ed Greshko wrote > > You may be running into the same bug others have That > is NFS > mounts > > not mounting at boot time. There is a bugzilla open for > it > > https://bugzilla.redhat.com/show_bug.cgi?id=692008 > > > > Try mounting manually. If that works, then you're > experiencing the > bug. > > > Is this the right mount command? > mount -t nfs > 192.168.1.14:/home/magnusg/Music /home/magnusg/Music > > I get this error message: > mount.nfs: Connection timed out > > > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Guidelines: > http://fedoraproject.org/wiki/Mailing_list_guidelines > > > -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: NFS issues
On 10/22/2011 08:07 PM, Gerhard Magnus wrote: >> >> >> Is this the right mount command? >> mount -t nfs >> 192.168.1.14:/home/magnusg/Music /home/magnusg/Music >> >> I get this error message: >> mount.nfs: Connection timed out Are you seeing anything in the server logs? Either selinux (sealert -b) or /var/log/messages? -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: NFS issues
On Sat, 22 Oct 2011 16:42:26 -0700 Gerhard Magnus wrote: > I get this error message: > mount.nfs: Connection timed out Try restarting the NFS server on the host system and then try mounting the filesystem on the client again. I get the impression that systemd somehow manages to start servers before the network is ready. I have a lot of stuff I had to move to rc.local and throw in a delay to get servers to start correctly. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: NFS issues
On 10/22/2011 04:42 PM, Gerhard Magnus wrote: > Is this the right mount command? > mount -t nfs 192.168.1.14:/home/magnusg/Music /home/magnusg/Music > If this partition is listed in /etc/fstab, you should be able to get away with this: mount /home/magnusg/Music or, if you really want to avoid typing errors: mount -a will mount everything in /etc/fstab. As far as the timeout goes, can you ping the machine? -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: NFS issues
On 10/22/2011 08:43 PM, Gerhard Magnus wrote: > > I didn't get anything running sealert -b. The widget "SELinux Alert > Browser" showed no alerts. In /var/log/messages I get this message > repeated at intervals: > Oct 22 17:37:49 PuteB mount[1460]: mount to NFS server '192.168.1.14' > failed: Connection refused, retrying > > This sounds like its on the client machine - was hoping for logs from the NFS server .. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Fedora 15 +scsi Solved
Bill Perry: >> It appears that my scsi card went bad during the hardware upgrade. >> >> Arg! Tom Horsley: > I'm convinced that hardware just sits around waiting for > a software upgrade so it can fail at the most confusing > possible time :-). It's not too surprising, in some cases... Often, a computer spends most of its time idling along, but an install causes it to do a moderately heavy workload for a prolonged period, and that can show up cooling faults, or be the straw that broke the camel's back in components that were on the verge of failing. And then there's computers that spend a year or two sitting on the shelf, then the user opens them up and rummages around inside. Subjecting it to physical stress (twisting the case, so cards walk out of the motherboard, or hairline fractures occur), and to static shocks. -- [tim@localhost ~]$ uname -r 2.6.27.25-78.2.56.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Samsung ML1640
On Fri, 2011-10-21 at 17:33 -0300, Fernando Cassia wrote: > Check ebay for Continuous Ink Systems (CIS) made in China. Then you > can buy ink in bulk (bottles) and refill automagically to your heart´s > content. Still doesn't get around the head clogging issues... I've used printers with heads built into the ink cartridge, and separate heads, they've all clogged up badly, and some very quickly. And the waste of expensive overpriced ink, during all the head cleaning cycles. It's a bad technology. -- [tim@localhost ~]$ uname -r 2.6.27.25-78.2.56.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Samsung ML1640
On Sun, Oct 23, 2011 at 00:42, Tim wrote: > I've used printers > with heads built into the ink cartridge, and separate heads, they've all > clogged up badly, and some very quickly. Well, I agree, to a degree, but there´s workarounds, like scheduling a print job of some picture every 10 days or so. Since I have my inkjets connected to a network print server, this is easy to do. FC -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
