[RESOLVED] Automount Messages and Possible Samba mount failure
-
pschaff
- Retired Moderator
- Posts: 18276
- Joined: 2006/12/13 20:15:34
- Location: Tidewater, Virginia, North America
- Contact:
Re: Automount Messages and Possible Samba mount failure
Nothing wrong with those DNS settings for [i]external[/i] name resolution, but if you want to resolve names on the LAN you need some kind of local DNS service, to use /etc/hosts. Windows has its own magic for handling this so that may muddy the waters. This is often provided by the router for the LAN that incorporates a DHCP server as well as DNS. If your situation does not fit this model then please describe it more fully.
Re: Automount Messages and Possible Samba mount failure
A check of the linsys router (WRT54GSV4) shows that it is set with DHCP enabled to a start IP of 192.168.1.100 with 50 users max.
It may or may not be related but when I do a linux server boot I see various things roll by, then I see a series
> - Broadcom UNDI
> - Broadcom Base Code PXE
> - Client MAC Address ####
> - DHCP .../
> and the / whirls through its various |/-\ for a while.
So presumably PXE is trying to find a DHCP server to boot from. However when I the control key on boot to go into the PXE configuration I don't see what I need to turn off DHCP. It is probably right there but I don't know what I'm looking at. It has been this way for quite a while, I just never got back to looking for where to turn off DHCP. I suspect it is in the main BIOS boot sequence. Again, this may not be related.
Alan D.
It may or may not be related but when I do a linux server boot I see various things roll by, then I see a series
> - Broadcom UNDI
> - Broadcom Base Code PXE
> - Client MAC Address ####
> - DHCP .../
> and the / whirls through its various |/-\ for a while.
So presumably PXE is trying to find a DHCP server to boot from. However when I the control key on boot to go into the PXE configuration I don't see what I need to turn off DHCP. It is probably right there but I don't know what I'm looking at. It has been this way for quite a while, I just never got back to looking for where to turn off DHCP. I suspect it is in the main BIOS boot sequence. Again, this may not be related.
Alan D.
-
pschaff
- Retired Moderator
- Posts: 18276
- Joined: 2006/12/13 20:15:34
- Location: Tidewater, Virginia, North America
- Contact:
Re: Automount Messages and Possible Samba mount failure
Have a look at [url=http://wiki.centos.org/TipsAndTricks/EmulateFixedAddressByDHCP]Emulate a fixed IP address using MAC address with DHCP[/url] and see if it gives you any ideas.
Re: Automount Messages and Possible Samba mount failure
[quote]
pschaff wrote:
Have a look at [url=http://wiki.centos.org/TipsAndTricks/EmulateFixedAddressByDHCP]Emulate a fixed IP address using MAC address with DHCP[/url] and see if it gives you any ideas.[/quote]
Thanks for the link, Phil. I did look that over and check my router was seen from the linux box with the /sbin/route -n It produced identical output as shown but with my routers 192. address, so presumably the server sees the router as a DHCP/DNS source. I did not implement DHCP hosting on the linux box. I still haven't found in my router where it associates MAC addresses relative to DHCP or DNS. I do have it access locked by MAC but that isn't what the sheet was implying. I'll need to research the router a bit more. It is also a bit odd that if the linux box is seeing the router as the DHCP/DNS source why it seems to take so long and not find DHCP on boot cycle.
Heh, heh, also the change I did according to the way to disable IPV6 now throws a red [FAILED] flag in the boot cycle for "ip6tables firewall rules. I probably need to disable the ipv6 firewall script as well somewhere.
More later,
Alan D.
pschaff wrote:
Have a look at [url=http://wiki.centos.org/TipsAndTricks/EmulateFixedAddressByDHCP]Emulate a fixed IP address using MAC address with DHCP[/url] and see if it gives you any ideas.[/quote]
Thanks for the link, Phil. I did look that over and check my router was seen from the linux box with the /sbin/route -n It produced identical output as shown but with my routers 192. address, so presumably the server sees the router as a DHCP/DNS source. I did not implement DHCP hosting on the linux box. I still haven't found in my router where it associates MAC addresses relative to DHCP or DNS. I do have it access locked by MAC but that isn't what the sheet was implying. I'll need to research the router a bit more. It is also a bit odd that if the linux box is seeing the router as the DHCP/DNS source why it seems to take so long and not find DHCP on boot cycle.
Heh, heh, also the change I did according to the way to disable IPV6 now throws a red [FAILED] flag in the boot cycle for "ip6tables firewall rules. I probably need to disable the ipv6 firewall script as well somewhere.
More later,
Alan D.
Re: Automount Messages and Possible Samba mount failure
Your server does not use your router for either DHCP or DNS.
Your DHCP server hands out addresses 192.168.1.100 thru 192.168.1.149, and your server has 192.168.1.21, which is outside that range and thus fixed in your ifcfg-eth0 file.
This is reflected by your /etc/resolv.conf, which would be rewritten on boot if you'd used DHCP (this can be avoided, but default behavior is to have dhcp rewrite it).
Please show the output of
[code]cat /etc/sysconfig/network-scripts/ifcfg-eth0[/code]
Something you could temporarily try is changing your /etc/resolv.conf file to read
[code]search magnoliaroad.net
#nameserver 66.28.xxx.xxx
#nameserver 69.67.xxx.xxx
nameserver 192.168.1.10[/code]
assuming 192.168.1.10 is your WRT54GSV4 Linksys router.
Again assuming that the Linksys knows about your provider's DNS server(s) (as it usually does) this should allow you to resolve both local end external names through the Linksys's caching DNS. Although it may not know about your server as it has not handed out its IP address. Assigning fixed IP-addresses through DHCP based on MAC address does not seem to be something this router can handle, at least the [url=http://homesupport.cisco.com/en-us/support/routers/WRT54GS]user guide[/url] has no references to that.
You may need to revert to using /etc/hosts for local name resolution, or the equivalent hosts file in Windows.
Please note that 8.8.8.8 (google DNS) is not in your /etc/resolv, did you put that as static DNS1 in the Linksys config? If yes, it is not being used, as you have no reference to the Linksys, unless you make the suggested change.
Your DHCP server hands out addresses 192.168.1.100 thru 192.168.1.149, and your server has 192.168.1.21, which is outside that range and thus fixed in your ifcfg-eth0 file.
This is reflected by your /etc/resolv.conf, which would be rewritten on boot if you'd used DHCP (this can be avoided, but default behavior is to have dhcp rewrite it).
Please show the output of
[code]cat /etc/sysconfig/network-scripts/ifcfg-eth0[/code]
Something you could temporarily try is changing your /etc/resolv.conf file to read
[code]search magnoliaroad.net
#nameserver 66.28.xxx.xxx
#nameserver 69.67.xxx.xxx
nameserver 192.168.1.10[/code]
assuming 192.168.1.10 is your WRT54GSV4 Linksys router.
Again assuming that the Linksys knows about your provider's DNS server(s) (as it usually does) this should allow you to resolve both local end external names through the Linksys's caching DNS. Although it may not know about your server as it has not handed out its IP address. Assigning fixed IP-addresses through DHCP based on MAC address does not seem to be something this router can handle, at least the [url=http://homesupport.cisco.com/en-us/support/routers/WRT54GS]user guide[/url] has no references to that.
You may need to revert to using /etc/hosts for local name resolution, or the equivalent hosts file in Windows.
Please note that 8.8.8.8 (google DNS) is not in your /etc/resolv, did you put that as static DNS1 in the Linksys config? If yes, it is not being used, as you have no reference to the Linksys, unless you make the suggested change.
Re: Automount Messages and Possible Samba mount failure
Howdy Rene'
Thanks for the response and information. Output for ifcfg-eth0 is
[code]
> cat /etc/sysconfig/network-scripts/ifcfg-eth0
# Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet PCI Express
DEVICE=eth0
BOOTPROTO=none
BROADCAST=192.168.1.255
HWADDR=00:18:8b:e7:56:f8
IPADDR=192.168.1.21
NETMASK=255.255.255.0
NETWORK=192.168.1.0
ONBOOT=yes
GATEWAY=192.168.1.10
TYPE=Ethernet
USERCTL=no
IPV6INIT=no
PEERDNS=yes
[/code]
You are right that I did not intend to have the router do DHCP for my machines that I assign fixed IPs for. Initially that was intended for use by guests to our network to allow them to have internet access by letting the router assign them a name/IP on the fly. I had come to the same conclusion about MAC addresses for the router for fixed IPs but given my planned use of DHAC maybe that isn't important.
I'm kind of inexperienced so I though that the server was picking up DNS from the router which does get it from the ISP. But if I am understanding this right that is just for outside names, not names in the 192 LAN. My resolve.conf looks like
[code]
search magnoliaroad.net
nameserver 66.28.xxx.xxx
nameserver 69.67.xxx.xxx
[/code]
Both the 66. and 69. are nameservers provided by the ISP. But again that is all in the outside. Is there any problem with including 192.168.1.10 pointing to the router on the inside LAN while also pointing to outside fixed IPs?
I did add the google DNS in the Linsys config. Remember that I have the Linux server set in the router's DMZ so I had thought that that did direct passthrough both ways for the server and it would be picking up all the router settings. Again, probably just my inexperience showing again.
And again thanks for the help and tips.
Alan D.
Thanks for the response and information. Output for ifcfg-eth0 is
[code]
> cat /etc/sysconfig/network-scripts/ifcfg-eth0
# Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet PCI Express
DEVICE=eth0
BOOTPROTO=none
BROADCAST=192.168.1.255
HWADDR=00:18:8b:e7:56:f8
IPADDR=192.168.1.21
NETMASK=255.255.255.0
NETWORK=192.168.1.0
ONBOOT=yes
GATEWAY=192.168.1.10
TYPE=Ethernet
USERCTL=no
IPV6INIT=no
PEERDNS=yes
[/code]
You are right that I did not intend to have the router do DHCP for my machines that I assign fixed IPs for. Initially that was intended for use by guests to our network to allow them to have internet access by letting the router assign them a name/IP on the fly. I had come to the same conclusion about MAC addresses for the router for fixed IPs but given my planned use of DHAC maybe that isn't important.
I'm kind of inexperienced so I though that the server was picking up DNS from the router which does get it from the ISP. But if I am understanding this right that is just for outside names, not names in the 192 LAN. My resolve.conf looks like
[code]
search magnoliaroad.net
nameserver 66.28.xxx.xxx
nameserver 69.67.xxx.xxx
[/code]
Both the 66. and 69. are nameservers provided by the ISP. But again that is all in the outside. Is there any problem with including 192.168.1.10 pointing to the router on the inside LAN while also pointing to outside fixed IPs?
I did add the google DNS in the Linsys config. Remember that I have the Linux server set in the router's DMZ so I had thought that that did direct passthrough both ways for the server and it would be picking up all the router settings. Again, probably just my inexperience showing again.
And again thanks for the help and tips.
Alan D.
Re: Automount Messages and Possible Samba mount failure
The eth0 config is more or less conform expectation; the PEERDNS entry is redundant as you do not use DHCP (and it has the default value anyway). PEERDNS=no stops dhcp from rewriting your /etc/resolv.conf, something I hinted at in my previous post.
You should be able to point /etc/resolv.conf to your router without issues, removing the ISP DNSs as those are already assigned to your router.
That way you have a single point of maintenance for DNS.
If static DNS config in the router (DNS1 thru DNS3) overrides the DHCP assignements, you could add the ISP DNSs to the other two entries in your router.
But you'll be using only your primary DNS, not all three of them, just like at the moment you only use the first DNS entry in /etc/resov.conf.
The extra DNS entries are 'fallback' entries, only used in case the primary DNS is not available, in which case the system will use the secondary, end eventually, the third.
As your router will not know about your server, you'll need to use the host files for local name resolution, unless you have a large number of boxes on the LAN, in which case a local DNS may be preferable from a maintenance point of view.
You should be able to point /etc/resolv.conf to your router without issues, removing the ISP DNSs as those are already assigned to your router.
That way you have a single point of maintenance for DNS.
If static DNS config in the router (DNS1 thru DNS3) overrides the DHCP assignements, you could add the ISP DNSs to the other two entries in your router.
But you'll be using only your primary DNS, not all three of them, just like at the moment you only use the first DNS entry in /etc/resov.conf.
The extra DNS entries are 'fallback' entries, only used in case the primary DNS is not available, in which case the system will use the secondary, end eventually, the third.
As your router will not know about your server, you'll need to use the host files for local name resolution, unless you have a large number of boxes on the LAN, in which case a local DNS may be preferable from a maintenance point of view.
Re: Automount Messages and Possible Samba mount failure
Howdy Rene',
I sincerely appreciate the detailed information, I'm keeping this info saved off for my edification. This really helps me understand what is going on with DNS and DHCP on the machine.
As per your suggestion, I will clean up my resolv.conf to have just the single point of contact to the router.
I had in the past sort of understood that I needed the hosts file for name resolution in the LAN. There are only three active machine and two earlier incarnations of RedHat, both now dormant but kept in case of needing a file. So my hosts looks like
[code]
> cat hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
::1 localhost6.localdomain6 localhost6
127.0.0.1 localhost.localdomain localhost dunwellguitar3
69.67.xxx.xxx dunwellguitar.com dunwellguitar
192.168.1.20 dunwellguitar2 dunwellguitar2
192.168.1.21 dunwellguitar3 dunwellguitar3
192.168.1.25 dunwell-lap dunwell-lap
[/code]
Where the 69.67 is the outside address of the router. DG2 is one of the earlier RH machines and I will just comment that one out. dunwell-lap is the Win7 machine. That also needs to be cleaned up since the laptop name has changed to DGLapWin7. Sigh, how do people keep track of all the files with all the various names and IPs. I keep copious sysadmin notes but still miss things like this when making some change like the laptop name or the router IP address.
I'll get that done later today and do a full restart to make sure it is getting things right throughout.
Alan (humble grasshopper) D.
I sincerely appreciate the detailed information, I'm keeping this info saved off for my edification. This really helps me understand what is going on with DNS and DHCP on the machine.
As per your suggestion, I will clean up my resolv.conf to have just the single point of contact to the router.
I had in the past sort of understood that I needed the hosts file for name resolution in the LAN. There are only three active machine and two earlier incarnations of RedHat, both now dormant but kept in case of needing a file. So my hosts looks like
[code]
> cat hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
::1 localhost6.localdomain6 localhost6
127.0.0.1 localhost.localdomain localhost dunwellguitar3
69.67.xxx.xxx dunwellguitar.com dunwellguitar
192.168.1.20 dunwellguitar2 dunwellguitar2
192.168.1.21 dunwellguitar3 dunwellguitar3
192.168.1.25 dunwell-lap dunwell-lap
[/code]
Where the 69.67 is the outside address of the router. DG2 is one of the earlier RH machines and I will just comment that one out. dunwell-lap is the Win7 machine. That also needs to be cleaned up since the laptop name has changed to DGLapWin7. Sigh, how do people keep track of all the files with all the various names and IPs. I keep copious sysadmin notes but still miss things like this when making some change like the laptop name or the router IP address.
I'll get that done later today and do a full restart to make sure it is getting things right throughout.
Alan (humble grasshopper) D.
Re: Automount Messages and Possible Samba mount failure
This thing still has me whipped. I tried the suggested repairs and did a reboot and now:
my /etc/hosts file looks like
[code]
> cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
::1 localhost6.localdomain6 localhost6
127.0.0.1 localhost.localdomain localhost dunwellguitar3
69.67.xxx.xxx dunwellguitar.com dunwellguitar
#192.168.1.20 dunwellguitar2 dunwellguitar2
192.168.1.21 dunwellguitar3 dunwellguitar3
192.168.1.25 DGLapWin7 DGLapWin7
[/code]
My /etc/resolv.conf is
[code]
> cat /etc/resolv.conf
search magnoliaroad.net
nameserver 192.168.1.10
[/code]
ifcfg.cfg is now
[code]
> cat /etc/sysconfig/network-scripts/ifcfg-eth0
# Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet PCI Express
DEVICE=eth0
BOOTPROTO=none
BROADCAST=192.168.1.255
HWADDR=00:18:8b:xx:xx
IPADDR=192.168.1.21
NETMASK=255.255.255.0
NETWORK=192.168.1.0
ONBOOT=yes
GATEWAY=192.168.1.10
TYPE=Ethernet
USERCTL=no
IPV6INIT=no
PEERDNS=yes
[/code]
To make sure that the backups from the Win7 machine were not in the picture I disabled them. The /var/log/messages for yesterday and this morning still has the problem messages as before
[code]
Feb 22 04:03:20 localhost automount[2386]: key "*" not found in map source(s).
Feb 22 04:03:20 localhost automount[2386]: create_udp_client:101: hostname lookup failed: Unknown host
Feb 22 04:03:20 localhost automount[2386]: create_tcp_client:341: hostname lookup failed: No address associated with name
Feb 22 04:03:20 localhost automount[2386]: lookup_mount: exports lookup failed for *
Feb 22 04:03:20 localhost automount[2386]: key "*" not found in map source(s).
Feb 22 05:05:01 localhost kernel: kjournald starting. Commit interval 5 seconds
Feb 22 05:05:01 localhost kernel: EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
Feb 22 05:05:01 localhost kernel: EXT3 FS on sdb1, internal journal
Feb 22 05:05:01 localhost kernel: EXT3-fs: mounted filesystem with ordered data mode.
Feb 22 05:51:14 localhost xinetd[2447]: START: imap pid=20134 from=128.138.140.30
Feb 22 05:51:21 localhost xinetd[2447]: EXIT: imap status=0 pid=20134 duration=7(sec)
Feb 22 06:53:07 localhost xinetd[2447]: START: imap pid=20295 from=128.138.140.30
Feb 22 07:00:17 localhost xinetd[2447]: EXIT: imap status=0 pid=20295 duration=430(sec)
Feb 22 08:35:59 localhost xinetd[2447]: START: imap pid=20546 from=128.138.140.30
Feb 22 08:35:59 localhost xinetd[2447]: EXIT: imap status=0 pid=20546 duration=0(sec)
Feb 22 08:36:01 localhost xinetd[2447]: START: imap pid=20547 from=128.138.140.30
Feb 22 08:36:03 localhost xinetd[2447]: EXIT: imap status=0 pid=20547 duration=2(sec)
Feb 22 13:11:07 localhost xinetd[2447]: START: imap pid=21287 from=128.138.140.30
Feb 22 13:11:09 localhost xinetd[2447]: EXIT: imap status=0 pid=21287 duration=2(sec)
Feb 23 04:03:22 localhost automount[2386]: key "*" not found in map source(s).
Feb 23 04:03:22 localhost automount[2386]: create_udp_client:101: hostname lookup failed: Unknown host
Feb 23 04:03:22 localhost automount[2386]: create_tcp_client:341: hostname lookup failed: No address associated with name
Feb 23 04:03:22 localhost automount[2386]: lookup_mount: exports lookup failed for *
Feb 23 04:03:22 localhost automount[2386]: key "*" not found in map source(s).
Feb 23 05:05:01 localhost kernel: kjournald starting. Commit interval 5 seconds
Feb 23 05:05:01 localhost kernel: EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
Feb 23 05:05:01 localhost kernel: EXT3 FS on sdb1, internal journal
Feb 23 05:05:01 localhost kernel: EXT3-fs: mounted filesystem with ordered data mode.
Feb 23 06:21:10 localhost xinetd[2447]: START: imap pid=24640 from=128.138.140.30
Feb 23 06:21:17 localhost xinetd[2447]: EXIT: imap status=0 pid=24640 duration=7(sec)
[/code]
The only cron job is for root and it is not running anything at 04:03:22. [and I see that I need to run shutdown -F to clean up my external backup drive connections again , need to do from the consol so I can watch though]
However, when I look in /var/log/maillog I now notice
[quote]
Feb 23 04:02:22 localhost sendmail[23823]: q1NB2KQI023823: from=root, size=4207, class=0, nrcpts=1, msgid=
, relay=root@localhost
Feb 23 04:02:22 localhost sendmail[24099]: q1NB2M0D024099: from=, size=4487, class=0, nrcpts=1, msgid=
, proto=ESMTP, daemon=MTA, relay=localhost.localdomain [127.0.0.1]
Feb 23 04:02:22 localhost sendmail[23823]: q1NB2KQI023823: to=root, ctladdr=root (0/0), delay=00:00:02, xdelay=00:00:00, mailer=relay, pri=34207,
relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (q1NB2M0D024099 Message accepted for delivery)
Feb 23 04:02:30 localhost sendmail[24100]: q1NB2M0D024099: to=dunwell@mric.net, ctladdr= (0/0), delay=00:00:08,
xdelay=00:00:07, mailer=esmtp, pri=34721, relay=mx03.mric.net. [208.139.195.122], dsn=2.0.0, stat=Sent (q1NB2N5X028901 Message accepted for delivery)
[/quote][Moderator edit: Chenged [i]code[/i] to [i]quote[/i] tags to wrap long lines.]
which matches the time but AFAICS the mail goes out ok (mailing my logwatch to me) and I receive the messages. /etc/aliases has the root mail set to
[code]
# Person who should get root's mail
#root: marc
#root: dunwell@jila.colorado.edu
root: dunwell@mric.net
[/code]
and that seems to be working.
I also mention in case it is related that the folks at mric.net, my ISP, were recently doing "something" related to rDNS that was rejecting these messages for a few days but now they are going through. Something related to their SPAM filtering that rejects hosts that don't resolve.
Again, if anyone sees any "AhHah's" or can suggest other log files or config files to check I'm open to all suggestions.
Alan D.
my /etc/hosts file looks like
[code]
> cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
::1 localhost6.localdomain6 localhost6
127.0.0.1 localhost.localdomain localhost dunwellguitar3
69.67.xxx.xxx dunwellguitar.com dunwellguitar
#192.168.1.20 dunwellguitar2 dunwellguitar2
192.168.1.21 dunwellguitar3 dunwellguitar3
192.168.1.25 DGLapWin7 DGLapWin7
[/code]
My /etc/resolv.conf is
[code]
> cat /etc/resolv.conf
search magnoliaroad.net
nameserver 192.168.1.10
[/code]
ifcfg.cfg is now
[code]
> cat /etc/sysconfig/network-scripts/ifcfg-eth0
# Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet PCI Express
DEVICE=eth0
BOOTPROTO=none
BROADCAST=192.168.1.255
HWADDR=00:18:8b:xx:xx
IPADDR=192.168.1.21
NETMASK=255.255.255.0
NETWORK=192.168.1.0
ONBOOT=yes
GATEWAY=192.168.1.10
TYPE=Ethernet
USERCTL=no
IPV6INIT=no
PEERDNS=yes
[/code]
To make sure that the backups from the Win7 machine were not in the picture I disabled them. The /var/log/messages for yesterday and this morning still has the problem messages as before
[code]
Feb 22 04:03:20 localhost automount[2386]: key "*" not found in map source(s).
Feb 22 04:03:20 localhost automount[2386]: create_udp_client:101: hostname lookup failed: Unknown host
Feb 22 04:03:20 localhost automount[2386]: create_tcp_client:341: hostname lookup failed: No address associated with name
Feb 22 04:03:20 localhost automount[2386]: lookup_mount: exports lookup failed for *
Feb 22 04:03:20 localhost automount[2386]: key "*" not found in map source(s).
Feb 22 05:05:01 localhost kernel: kjournald starting. Commit interval 5 seconds
Feb 22 05:05:01 localhost kernel: EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
Feb 22 05:05:01 localhost kernel: EXT3 FS on sdb1, internal journal
Feb 22 05:05:01 localhost kernel: EXT3-fs: mounted filesystem with ordered data mode.
Feb 22 05:51:14 localhost xinetd[2447]: START: imap pid=20134 from=128.138.140.30
Feb 22 05:51:21 localhost xinetd[2447]: EXIT: imap status=0 pid=20134 duration=7(sec)
Feb 22 06:53:07 localhost xinetd[2447]: START: imap pid=20295 from=128.138.140.30
Feb 22 07:00:17 localhost xinetd[2447]: EXIT: imap status=0 pid=20295 duration=430(sec)
Feb 22 08:35:59 localhost xinetd[2447]: START: imap pid=20546 from=128.138.140.30
Feb 22 08:35:59 localhost xinetd[2447]: EXIT: imap status=0 pid=20546 duration=0(sec)
Feb 22 08:36:01 localhost xinetd[2447]: START: imap pid=20547 from=128.138.140.30
Feb 22 08:36:03 localhost xinetd[2447]: EXIT: imap status=0 pid=20547 duration=2(sec)
Feb 22 13:11:07 localhost xinetd[2447]: START: imap pid=21287 from=128.138.140.30
Feb 22 13:11:09 localhost xinetd[2447]: EXIT: imap status=0 pid=21287 duration=2(sec)
Feb 23 04:03:22 localhost automount[2386]: key "*" not found in map source(s).
Feb 23 04:03:22 localhost automount[2386]: create_udp_client:101: hostname lookup failed: Unknown host
Feb 23 04:03:22 localhost automount[2386]: create_tcp_client:341: hostname lookup failed: No address associated with name
Feb 23 04:03:22 localhost automount[2386]: lookup_mount: exports lookup failed for *
Feb 23 04:03:22 localhost automount[2386]: key "*" not found in map source(s).
Feb 23 05:05:01 localhost kernel: kjournald starting. Commit interval 5 seconds
Feb 23 05:05:01 localhost kernel: EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
Feb 23 05:05:01 localhost kernel: EXT3 FS on sdb1, internal journal
Feb 23 05:05:01 localhost kernel: EXT3-fs: mounted filesystem with ordered data mode.
Feb 23 06:21:10 localhost xinetd[2447]: START: imap pid=24640 from=128.138.140.30
Feb 23 06:21:17 localhost xinetd[2447]: EXIT: imap status=0 pid=24640 duration=7(sec)
[/code]
The only cron job is for root and it is not running anything at 04:03:22. [and I see that I need to run shutdown -F to clean up my external backup drive connections again , need to do from the consol so I can watch though]
However, when I look in /var/log/maillog I now notice
[quote]
Feb 23 04:02:22 localhost sendmail[23823]: q1NB2KQI023823: from=root, size=4207, class=0, nrcpts=1, msgid=
, relay=root@localhost
Feb 23 04:02:22 localhost sendmail[24099]: q1NB2M0D024099: from=, size=4487, class=0, nrcpts=1, msgid=
, proto=ESMTP, daemon=MTA, relay=localhost.localdomain [127.0.0.1]
Feb 23 04:02:22 localhost sendmail[23823]: q1NB2KQI023823: to=root, ctladdr=root (0/0), delay=00:00:02, xdelay=00:00:00, mailer=relay, pri=34207,
relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (q1NB2M0D024099 Message accepted for delivery)
Feb 23 04:02:30 localhost sendmail[24100]: q1NB2M0D024099: to=dunwell@mric.net, ctladdr= (0/0), delay=00:00:08,
xdelay=00:00:07, mailer=esmtp, pri=34721, relay=mx03.mric.net. [208.139.195.122], dsn=2.0.0, stat=Sent (q1NB2N5X028901 Message accepted for delivery)
[/quote][Moderator edit: Chenged [i]code[/i] to [i]quote[/i] tags to wrap long lines.]
which matches the time but AFAICS the mail goes out ok (mailing my logwatch to me) and I receive the messages. /etc/aliases has the root mail set to
[code]
# Person who should get root's mail
#root: marc
#root: dunwell@jila.colorado.edu
root: dunwell@mric.net
[/code]
and that seems to be working.
I also mention in case it is related that the folks at mric.net, my ISP, were recently doing "something" related to rDNS that was rejecting these messages for a few days but now they are going through. Something related to their SPAM filtering that rejects hosts that don't resolve.
Again, if anyone sees any "AhHah's" or can suggest other log files or config files to check I'm open to all suggestions.
Alan D.
-
pschaff
- Retired Moderator
- Posts: 18276
- Joined: 2006/12/13 20:15:34
- Location: Tidewater, Virginia, North America
- Contact:
Re: Automount Messages and Possible Samba mount failure
[i]Code[/i] sections will not wrap. You can wrap manually, or use [i]quote[/i] tags, as I changed them to.
I'm a bit confused after this long winding [d]road[/d] thread. Are there actual demonstrated problems, or are you just worried about the log messages?
I'm a bit confused after this long winding [d]road[/d] thread. Are there actual demonstrated problems, or are you just worried about the log messages?