Re: [CentOS] ntfs-3g
On Wed, 2013-03-13 at 23:36 -0700, Al Sparks wrote: > I'm looking for ntfs-3g. I'm getting lots of hits through google, but I'm > suspicious of some of the sites. > > The one rpm I downloaded from rpmfind wouldn't install because of some > missing library. Where's a good place to get the tarball? > === Al > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos Al, You can use the package from epel repo Installed Packages ntfs-3g.x86_64 2:2011.4.12-5.el6 @epel -- Kind Regards Earl Ramirez GPG Key: http://trinipino.com/PublicKey.asc signature.asc Description: This is a digitally signed message part ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] ntfs-3g
hello, I install it on every laptop from epel repo. I tried rpmforge repo as wel, that would sometimes give me read-only usb connectivity. Greetings, J. Op 14-03-13 07:36, Al Sparks schreef: > I'm looking for ntfs-3g. I'm getting lots of hits through google, but I'm > suspicious of some of the sites. > > The one rpm I downloaded from rpmfind wouldn't install because of some > missing library. Where's a good place to get the tarball? > === Al > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] ntfs-3g
Try yum install ntfs-3g On Mar 14, 2013 2:36 AM, "Al Sparks" wrote: > I'm looking for ntfs-3g. I'm getting lots of hits through google, but I'm > suspicious of some of the sites. > > The one rpm I downloaded from rpmfind wouldn't install because of some > missing library. Where's a good place to get the tarball? > === Al > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Adding third party driver at installation time.
Hi, I have a PCIe storage device. My driver registers this device as a block device in linux. My block device is working fine under linux. Following are the steps which I used for Centos installation on my storage device: 1) During Centos installation time and before scanning of my storage device, I loaded the driver from command line(By pressing Ctrl + Alt + F2) from USB disk. 2) Post loading of drivers, the installation proceeded successfully on my storage device. Query: 1) How to add my driver as part of installed initrd image at the installation time itself.[because root file system also installed on same device] Waiting for positive reply Thanks & Regards, Sateesh ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Kernel panic after update to 6.4
On 2013-03-13, Johnny Hughes wrote: (...) > On 03/13/2013 04:19 PM, Liam O'Toole wrote: >> On 2013-03-13, Emmett Culley wrote: >> >> (...) >> >>> So let's start again. >>> >>> Kernel panic - Not syncing: Attempted to kill init! >>> Pid: 1, comm: init not tainted: 2.6.32-358.0.1.el6.x86_64 #1 >>> >>> After yum upgrade --enablerepo=3Depel on two of five machines, one of = > which is the host for the three VM's that succeeded and the one that fail= > ed, just as the host. >>> >>> I have a screen shot of that VM's boot failure, but I don't know the p= > roper way to include it in a post. >>> >>> I've uninstalled that kernel and ran yum upgrade again, it still fails= > on that kernel, on both the host and the VM. I suppose the good thing i= > s that it happened on a VM guest that is not critical, so I don't have to= > experiment with the host that has four important guests running on it. >>> >>> Any ideas? >>> >>> Emmett >> I saw this problem on one machine I upgraded from 6.3 to 6.4 recently. >> When I boot it in verbose mode I see the following messages: >> >> dracut: /proc/misc: No entry for device-mapper found >> dracut: Failure to communicate with kernel device-mapper driver >> >> which led me to the following bug report: >> >> http://bugs.centos.org/view.php?id=3D6304 >> >> Just today kernel 2.6.32-358.2.1 became available. The problem is still= > >> present, but only on the same one machine. >> > > What does this command say: > > rpm -q device-mapper The output is device-mapper-1.02.77-9.el6.i686 Ditto on the machines which are *not* affected. -- Liam ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Kernel panic after update to 6.4
On 2013-03-13, Johnny Hughes wrote: (...) > On 03/13/2013 05:17 PM, Johnny Hughes wrote: >> On 03/13/2013 04:19 PM, Liam O'Toole wrote: >>> On 2013-03-13, Emmett Culley wrote: >>> >>> (...) >>> So let's start again. Kernel panic - Not syncing: Attempted to kill init! Pid: 1, comm: init not tainted: 2.6.32-358.0.1.el6.x86_64 #1 After yum upgrade --enablerepo=3Depel on two of five machines, one of= > which is the host for the three VM's that succeeded and the one that fai= > led, just as the host. I have a screen shot of that VM's boot failure, but I don't know the = > proper way to include it in a post. I've uninstalled that kernel and ran yum upgrade again, it still fail= > s on that kernel, on both the host and the VM. I suppose the good thing = > is that it happened on a VM guest that is not critical, so I don't have t= > o experiment with the host that has four important guests running on it. Any ideas? Emmett >>> I saw this problem on one machine I upgraded from 6.3 to 6.4 recently.= > >>> When I boot it in verbose mode I see the following messages: >>> >>> dracut: /proc/misc: No entry for device-mapper found >>> dracut: Failure to communicate with kernel device-mapper driver >>> >>> which led me to the following bug report: >>> >>> http://bugs.centos.org/view.php?id=3D6304 >>> >>> Just today kernel 2.6.32-358.2.1 became available. The problem is stil= > l >>> present, but only on the same one machine. >>> >> This file exists in the kernel: >> /lib/modules/2.6.32-358.2.1.el6.x86_64/kernel/drivers/md/dm-mod.ko >> >> Somehow it seems that in some machines it is not making it into the ini= > trd. > > Try this command where the kernel is installed and not booting (when > booted into a kernel that works): > > lsinitrd /boot/initramfs-2.6.32-358.2.1.el6.x86_64.img | grep dm-mod > > (if you have one of the other 358 kernels installed, use that version > instead of2.6.32-358.2.1.el6.x86_64 ) > Here you go: $ uname -r && lsinitrd /boot/initramfs-2.6.32-358.2.1.el6.i686.img | grep dm-mod 2.6.32-279.22.1.el6.i686 -rwxr--r-- 1 root root 106212 Mar 13 17:11 lib/modules/2.6.32-358.2.1.el6.i686/kernel/drivers/md/dm-mod.ko So the module appears to be present in the initrd. The only distinguishing feature I can think of in the machine that is failing is that it has a solid-state drive. Relevant? -- Liam ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Postfix (Roundcube client) sends mail, but not able to receive
On 03/14/2013 12:33 AM, Austin Einter wrote: > Hi Les Mikesell > The rpm installed in my m/c is *amavisd-new-2.6.4-2.el6.noarch*. > > I believe it is from epel (I have epel repo enabled). > > > Is it incompatible? If you ARE using the amavisd from epel, you should follow the instructions from: http://wiki.centos.org/HowTos/Amavisd not http://campworld.net/thewiki/pmwiki.php/LinuxServersCentOS/Cent6VirtMailServer as it uses rpmfusion, if I recall right. But definitely not epel. Part of the reason I did not follow its anti-spam portion. The install should have been: yum install amavisd-new clamav clamav-devel clamd spamassassin Then there are group permission problems. I have entered a bug report for epel on this: 906396 You need to: gpasswd -a clam amavis chkconfig clamd on chkconfig amavisd on Then there are some specific run directories that have to match. I am in the Orlando airport and they are blocking my SSH back to my server to get the correct changes but my old notes with me say something to the effect: in /etc/amavisd/amavisd.conf change .pid to match in /etc/clamd.conf But I can't get to the exact info until I get home this afternoon. Then the var directory is not created by the rpm. You need to: cd /var/spool/amavisd mkdir var chown amavis:amavis var chmod 700 var Though one follow soujourner said 750 for the whole tree. Finally: sa-update service amavisd start service clamd start chkconfig amavisd on Then test with: telnet localhost 10024 ehlo localhost quit telnet localhost 10025 ehlo localhost quit postconf -e 'content_filter=amavisfeed:[127.0.0.1]:10024' cd /usr/share/doc/amavisd-new-2.6.4/test-messages perl -pe 's/./chr(ord($&)^255)/sge' http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] SOLUTION: Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller - GDM login doesn't show up
Στις , Frank Cox έγραψε: > On Wed, 13 Mar 2013 21:54:26 + > Nux! wrote: > >> What laptop is this? > > It isn't a laptop. It's a small-format "white box" computer in a > case that's > about half of the height and width of a standard computer case. You > plug any > analog monitor into it. I have loaded CentOS 5.x on an Intel D525 CPU (I believe) motherboard a while back and no such "special" treatment was required. Are you sure that this is not just a specific problem with the box you are using? Andreas ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Kernel panic after update to 6.4
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/13/2013 05:52 PM, Nux! wrote: > On 12.03.2013 20:41, Emmett Culley wrote: >> After successfully updating three CentOS 6.3 VM guests to 6.4 I decided >> to update the host as well. And it failed to boot. >> >> Kernel panic - Not syncing: Attempted to kill init! Pid: 1, comm: init >> not tainted: 2.6.32-358.2.1.el6.x86_64 #1 Plus a call trace I couldn't >> see > > Is selinux on? If you boot the new kernel with selinux=0 does the panic > happen? I had this happen to me recently. > You can leave SELinux on in permissive mode using enforcing=0. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlFBx90ACgkQrlYvE4MpobNW9QCglp3IoeXleJWrxbMwQsngaf6w mR0AoMBamEd6Zcz+h/mbtrLG11bnMLCW =ZqVF -END PGP SIGNATURE- ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Shorewall and upgrade from 6.3 to 6.4
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/14/2013 01:03 AM, Kahlil Hodgson wrote: > On 14/03/13 06:23, Gordon Messmer wrote: >> On 03/12/2013 04:07 PM, Kahlil Hodgson wrote: >>> If you are upgrading from 6.3 to 6.4 and you use shorewall, you will >>> want to run >>> >>> restorecon -Rv /sbin >> >> That's odd. Part of the selinux postinstall script involves running >> "fixfiles" on any files whose context has changed. I confirmed that the >> iptables contexts changed when I ran restorecon on one system, but I >> can't understand why they weren't fixed by the postinstall script. > > My thoughts exactly. Just doubled checked the postinstall script and can't > see any obvious bugs. Hmmm ... > > If I compare the old and new file_context files ... > > diff file_contexts.new file_contexts.old | grep ip6?tables-multi >> /sbin/ip6?tables-multi -- system_u:object_r:iptables_exec_t:s0 > < /sbin/ip6?tables-multi.*-- system_u:object_r:iptables_exec_t:s0 > > so the postinstall script runs (esentially) > > fixfiles -C file_contexts.old restore > > which tries to fix the context for a /sbin/ip6?tables-multi which does not > exist on the updated system (which now uses alternatives trickery to > version these). > > K > There is a bug in the fixfiles script which was causing triggered by the weird regex, so the change was not being caught. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlFByCEACgkQrlYvE4MpobOOBgCfcvBLYB8iDyofREAx5UHHUC2V r5wAoJnJzFIlX5EeiAg1po9ahl7JztbW =RVIh -END PGP SIGNATURE- ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] SOLUTION: Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller - GDM login doesn't show up
On 03/14/2013 08:24 AM, Andreas K. wrote: > , Frank Cox ??: >> On Wed, 13 Mar 2013 21:54:26 + >> Nux! wrote: >> >>> What laptop is this? >> It isn't a laptop. It's a small-format "white box" computer in a >> case that's >> about half of the height and width of a standard computer case. You >> plug any >> analog monitor into it. > I have loaded CentOS 5.x on an Intel D525 CPU (I believe) motherboard a > while > back and no such "special" treatment was required. Are you sure that > this is not > just a specific problem with the box you are using? > > Andreas > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > Or the monitor not responding to EDID queries. What shows in the Xorg log. -- Stephen Clark *NetWolves* Director of Technology Phone: 813-579-3200 Fax: 813-882-0209 Email: steve.cl...@netwolves.com http://www.netwolves.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] moderate rant un updates
So, another admin I work with rolled out most (but not kernel) updates to 6.4... but including xorg. I log out the end of the day, and I'm hosed - no X. Now, my not-two-year-old workstation has an nvidia card, and I'd installed kmod-nvidia from elrepo. I figured I'd fix my problem by finishing the upgrade and rebooting. Nope. I try to upgrade kmod-nvidia from elrepo. Anyone got any good explanations as to why they'd put kmod-nvidia-310.40 in the repo, with the previous version not obvious... AND NOT HAVE THE *REQUIRED* nvidia-x11-drv-310.40 in there? Why not wait until both pieces could be uploaded, since kmod-nividia WILL NOT INSTALL without the other...? I then stupidly uninstalled the previous kmod-nvidia & nvidia-x11-drv, hoping it would allow a good install. Nope. Found the proprietary installer on the NVidia site, and I'm up. On a related note, does anyone have a link to a howto build the NVidia proprietary driver on a kernel that's *not* running, so we could prebuild it before the reboot? I see there are options in the script, but no examples. Also, is dkms coming in, or deprecated? mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Kernel panic after update to 6.4
On 03/14/2013 05:17 AM, Liam O'Toole wrote: > On 2013-03-13, Johnny Hughes wrote: > > (...) > >> On 03/13/2013 05:17 PM, Johnny Hughes wrote: >>> On 03/13/2013 04:19 PM, Liam O'Toole wrote: On 2013-03-13, Emmett Culley wrote: (...) > So let's start again. > > Kernel panic - Not syncing: Attempted to kill init! > Pid: 1, comm: init not tainted: 2.6.32-358.0.1.el6.x86_64 #1 > > After yum upgrade --enablerepo=3Depel on two of five machines, one of= >> which is the host for the three VM's that succeeded and the one that fai= >> led, just as the host. > I have a screen shot of that VM's boot failure, but I don't know the = >> proper way to include it in a post. > I've uninstalled that kernel and ran yum upgrade again, it still fail= >> s on that kernel, on both the host and the VM. I suppose the good thing = >> is that it happened on a VM guest that is not critical, so I don't have t= >> o experiment with the host that has four important guests running on it. > Any ideas? > > Emmett I saw this problem on one machine I upgraded from 6.3 to 6.4 recently.= When I boot it in verbose mode I see the following messages: dracut: /proc/misc: No entry for device-mapper found dracut: Failure to communicate with kernel device-mapper driver which led me to the following bug report: http://bugs.centos.org/view.php?id=3D6304 Just today kernel 2.6.32-358.2.1 became available. The problem is stil= >> l present, but only on the same one machine. >>> This file exists in the kernel: >>> /lib/modules/2.6.32-358.2.1.el6.x86_64/kernel/drivers/md/dm-mod.ko >>> >>> Somehow it seems that in some machines it is not making it into the ini= >> trd. >> >> Try this command where the kernel is installed and not booting (when >> booted into a kernel that works): >> >> lsinitrd /boot/initramfs-2.6.32-358.2.1.el6.x86_64.img | grep dm-mod >> >> (if you have one of the other 358 kernels installed, use that version >> instead of2.6.32-358.2.1.el6.x86_64 ) >> > Here you go: > > $ uname -r && lsinitrd /boot/initramfs-2.6.32-358.2.1.el6.i686.img | > grep dm-mod > 2.6.32-279.22.1.el6.i686 > -rwxr--r-- 1 root root 106212 Mar 13 17:11 > lib/modules/2.6.32-358.2.1.el6.i686/kernel/drivers/md/dm-mod.ko > > So the module appears to be present in the initrd. > > The only distinguishing feature I can think of in the machine that is > failing is that it has a solid-state drive. Relevant? Maybe ... try this (everything done as root): Boot on a kernel that works and do this: 1. Backup you current initrd: cp -a /boot/initramfs-2.6.32-358.2.1.el6.x86_64.img /boot/initramfs-2.6.32-358.2.1.el6.x86_64.img.bak 2. Go to this directory: cd /lib/modules/2.6.32-358.2.1.el6.x86_64/kernel/drivers/md/ 3. Figure out the md modules loaded in the old kernel: lsmod | grep dm_ in my case, that output would be this: [root@localhost md]# lsmod | grep dm_ dm_round_robin 2525 0 dm_multipath17756 1 dm_round_robin dm_mirror 14133 0 dm_region_hash 12085 1 dm_mirror dm_log 9930 2 dm_mirror,dm_region_hash dm_mod82839 12 dm_multipath,dm_mirror,dm_log (note, dm-mod and dm_mod are the same thing) 5. Do an file list and make sure all the modules you need to include (in my case the 6 in column 1): ls Note: make sure all the modules are listed ad you see the file names (should be for me: dm-round-robin.ko, dm-multipath.ko, dm-mirror.ko, dm-region-hash.ko, dm-log.ko, dm-mod.ko) 4. Create a new initrd with all the relevant md modules preloaded (in my case, this command line ... preload only the modules you need from your list .. again, have to do this as root): mkinitrd -f --preload=dm_round_robin --preload=dm_multipath --preload=dm_mirror --preload=dm_region_hash --preload=dm_log --preload=dm_mod /boot/initramfs-2.6.32-358.2.1.el6.x86_64.img 2.6.32-358.2.1.el6.x86_64 Note: The above mkinitrd command (and all the other commands) should be entered all on one line, I am sure it will wrap when posted. 5. This may not work, because there may need to be some other things loaded that are not, like the disc controller's kernel module driver, etc. What I think is going on is either something has been removed from this kernel that existed before ... OR ... something is being mis-detected with this kernel on your machine. signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] moderate rant un updates
On Mar 14, 2013, at 10:17 AM, m.r...@5-cent.us wrote: > So, another admin I work with rolled out most (but not kernel) > updates to > 6.4... but including xorg. I log out the end of the day, and I'm > hosed - > no X. > > Now, my not-two-year-old workstation has an nvidia card, and I'd > installed > kmod-nvidia from elrepo. Which card? > I try to upgrade kmod-nvidia from elrepo. Anyone got any good > explanations > as to why they'd put kmod-nvidia-310.40 in the repo, with the previous > version not obvious... You may need the legacy version; this is clearly documented on the current elrepo wiki pages about their nvidia modules. If you do, you need to: yum install nvidia-x11-drv-304xx and all should be good. > Found the proprietary installer on the NVidia site, and I'm up. > > Unnecessary. You need the elrepo nvidia version detector to see if you need the 304 legacy driver. > Also, is dkms coming in, or deprecated? Deprecated. The elrepo kmod works fine on any EL6 kernel thus far; my laptop, which needs the 304 legacy driver, updated to CentOS 6.4 just fine, before any elrepo updates. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] moderate rant un updates
On 03/14/2013 09:17 AM, m.r...@5-cent.us wrote: > So, another admin I work with rolled out most (but not kernel) updates to > 6.4... but including xorg. I log out the end of the day, and I'm hosed - > no X. > > Now, my not-two-year-old workstation has an nvidia card, and I'd installed > kmod-nvidia from elrepo. I figured I'd fix my problem by finishing the > upgrade and rebooting. > > Nope. > > I try to upgrade kmod-nvidia from elrepo. Anyone got any good explanations > as to why they'd put kmod-nvidia-310.40 in the repo, with the previous > version not obvious... AND NOT HAVE THE *REQUIRED* nvidia-x11-drv-310.40 > in there? Why not wait until both pieces could be uploaded, since > kmod-nividia WILL NOT INSTALL without the other...? > > I then stupidly uninstalled the previous kmod-nvidia & nvidia-x11-drv, > hoping it would allow a good install. > > Nope. > > Found the proprietary installer on the NVidia site, and I'm up. > > > On a related note, does anyone have a link to a howto build the NVidia > proprietary driver on a kernel that's *not* running, so we could prebuild > it before the reboot? I see there are options in the script, but no > examples. > > Also, is dkms coming in, or deprecated? None of those modules are in CentOS, but a 3rd party repo. How about you test your setup and how 3rd party repos interact with it ... THEN ask on the 3rd party repo's own mailing list how or why their packages no longer work with the update? signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Mounting USB drives read-only by default?
Is it possible to configure the automounting of USB drives to mount read-only? Is there some gconf/udev/udisks/hal/whatever setting to alter the default mount options when USB disks are plugged in by users? Thanks James Pearson ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] moderate rant un updates
Am 14.03.2013 15:17, schrieb m.r...@5-cent.us:
> On a related note, does anyone have a link to a howto build the NVidia
> proprietary driver on a kernel that's *not* running, so we could prebuild
> it before the reboot? I see there are options in the script, but no
> examples.
No link, but while I was still using the proprietary driver I did it
like this:
${NVDRV}.run -sKk ${KERNELRELEASE}
--
Tilman Schmidt
Phoenix Software GmbH
Bonn, Germany
signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] moderate rant un updates
On 14.03.2013 14:17, m.r...@5-cent.us wrote: > So, another admin I work with rolled out most (but not kernel) updates > to > 6.4... but including xorg. I log out the end of the day, and I'm hosed > - > no X. Install and run nvidia-detect from Elrepo, it will tell you which packages you need to install. HTH -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] moderate rant un updates
Sorry, clicked "send" too soon.
Am 14.03.2013 15:37, schrieb Tilman Schmidt:
> Am 14.03.2013 15:17, schrieb m.r...@5-cent.us:
>> On a related note, does anyone have a link to a howto build the NVidia
>> proprietary driver on a kernel that's *not* running, so we could prebuild
>> it before the reboot? I see there are options in the script, but no
>> examples.
>
> No link, but while I was still using the proprietary driver I did it
> like this:
>
> ${NVDRV}.run -sKk ${KERNELRELEASE}
That was from a kernel install script that had previously set
${KERNELRELEASE} to the name of the module directory and
${NVDRV} to the base name of the nVidia installer. So the
actual command would look something like this:
~/Download/NVIDIA-Linux-x86_64-270.41.06.run -sKk 2.6.37.6-24-desktop
HTH
T.
--
Tilman Schmidt
Phoenix Software GmbH
Bonn, Germany
signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] moderate rant un updates
Lamar Owen wrote: > On Mar 14, 2013, at 10:17 AM, m.r...@5-cent.us wrote: > >> So, another admin I work with rolled out most (but not kernel) >> updates to 6.4... but including xorg. I log out the end of the day, and I'm >> hosed - no X. >> >> Now, my not-two-year-old workstation has an nvidia card, and I'd >> installed kmod-nvidia from elrepo. > > Which card? GF100GL/Quadro 4000 > >> I try to upgrade kmod-nvidia from elrepo. Anyone got any good >> explanations as to why they'd put kmod-nvidia-310.40 in the repo, with the previous >> version not obvious... > > You may need the legacy version; this is clearly documented on the > current elrepo wiki pages about their nvidia modules. Nope, it does *not* use the legacy version. >> Found the proprietary installer on the NVidia site, and I'm up. >> >> Also, is dkms coming in, or deprecated? > > Deprecated. The elrepo kmod works fine on any EL6 kernel thus far; > my laptop, which needs the 304 legacy driver, updated to CentOS 6.4 > just fine, before any elrepo updates. Ah, thanks on the dkms. So I'm back to figuring out a script to automagically build the driver when the user's workstation reboots (and make sure it prints out a warm fuzzy so they don't worry while it does it). mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Kernel panic after update to 6.4
On 03/12/2013 05:08 PM, Emmett Culley wrote: > On 03/12/2013 04:23 PM, lists-centos wrote: >> >> >> Original Message >>> Date: Tuesday, March 12, 2013 04:05:28 PM -0700 >>> From: Emmett Culley >>> To: centos@centos.org >>> Cc: >>> Subject: Re: [CentOS] Kernel panic after update to 6.4 >>> >>> On 03/12/2013 01:48 PM, Akemi Yagi wrote: On Tue, Mar 12, 2013 at 1:41 PM, Emmett Culley wrote: > After successfully updating three CentOS 6.3 VM guests to 6.4 I > decided to update the host as well. And it failed to boot. > > Kernel panic - Not syncing: Attempted to kill init! > Pid: 1, comm: init not tainted: 2.6.32-358.2.1.el6.x86_64 #1 At the time of this writing, CentOS kernel 2.6.32-358.2.1.el6 is not out yet. Where did you get this one from ??? Did you build it yourself? I figured out that in both failure cases the "yum update" was never completed as I had to run yum-complete-transaction on both. And doing that and re-installing the 358.0.1 had the same boot failures. Yesterday I did another update which installed the 358.2.1 kernel, which booted. So I guess I'll attempt to update the host machine. I don't know what happened, but it seems to be resolved. Emmett ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] moderate rant un updates
Tilman Schmidt wrote:
> Sorry, clicked "send" too soon.
>
> Am 14.03.2013 15:37, schrieb Tilman Schmidt:
>> Am 14.03.2013 15:17, schrieb m.r...@5-cent.us:
>>> On a related note, does anyone have a link to a howto build the NVidia
>>> proprietary driver on a kernel that's *not* running, so we could
>>> prebuild
>>> it before the reboot? I see there are options in the script, but no
>>> examples.
>>
>> No link, but while I was still using the proprietary driver I did it
>> like this:
>>
>> ${NVDRV}.run -sKk ${KERNELRELEASE}
>
> That was from a kernel install script that had previously set
> ${KERNELRELEASE} to the name of the module directory and
> ${NVDRV} to the base name of the nVidia installer. So the
> actual command would look something like this:
>
> ~/Download/NVIDIA-Linux-x86_64-270.41.06.run -sKk 2.6.37.6-24-desktop
>
> HTH
It does, indeed. Thanks a lot, Tillman, that's what I needed (I'll check
to make sure it doesn't replace xorg.conf - a lot of us need the
proprietary driver because we use two monitors, and *bleah* nouveau
doesn't support twinview).
mark
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] moderate rant un updates
On Thu, Mar 14, 2013 at 8:03 AM, wrote: > a lot of us need the > proprietary driver because we use two monitors, and *bleah* nouveau > doesn't support twinview). > >mark Then you want to read this CentOS *FAQ*: http://wiki.centos.org/FAQ/CentOS6#head-012846a4e422267a34e81c4c905654fc8f36ffaf Akemi ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] moderate rant un updates
Johnny Hughes wrote: > On 03/14/2013 09:17 AM, m.r...@5-cent.us wrote: >> So, another admin I work with rolled out most (but not kernel) updates >> to 6.4... but including xorg. I log out the end of the day, and I'm hosed - >> no X. >> I try to upgrade kmod-nvidia from elrepo. Anyone got any good >> explanations >> as to why they'd put kmod-nvidia-310.40 in the repo, with the previous >> version not obvious... AND NOT HAVE THE *REQUIRED* nvidia-x11-drv-310.40 >> in there? Why not wait until both pieces could be uploaded, since >> kmod-nividia WILL NOT INSTALL without the other...? >> Also, is dkms coming in, or deprecated? > > None of those modules are in CentOS, but a 3rd party repo. That's fine. I found it annoying, but was trying to figure out whether to set that up with the proprietary driver or not. Thanks. > > How about you test your setup and how 3rd party repos interact with it > ... THEN ask on the 3rd party repo's own mailing list how or why their > packages no longer work with the update? I'd Have Been Glad To Test First... but read the first para, above Actually, also, I note that this does *not* happen with CentOS base; I just can't imagine why someone would do something that stupid as elrepo seems to have. mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Kernel panic after update to 6.4
On 2013-03-14, Johnny Hughes wrote: (...) > Maybe ... try this (everything done as root): > > Boot on a kernel that works and do this: > > 1. Backup you current initrd: > > cp -a /boot/initramfs-2.6.32-358.2.1.el6.x86_64.img > /boot/initramfs-2.6.32-358.2.1.el6.x86_64.img.bak OK. > > 2. Go to this directory: > > cd /lib/modules/2.6.32-358.2.1.el6.x86_64/kernel/drivers/md/ For me the corresponding directory is /lib/modules/2.6.32-358.2.1.el6.i686/kernel/drivers/md. > > 3. Figure out the md modules loaded in the old kernel: > > lsmod | grep dm_ > > in my case, that output would be this: > > [root@localhost md]# lsmod | grep dm_ > dm_round_robin 2525 0 > dm_multipath17756 1 dm_round_robin > dm_mirror 14133 0 > dm_region_hash 12085 1 dm_mirror > dm_log 9930 2 dm_mirror,dm_region_hash > dm_mod82839 12 dm_multipath,dm_mirror,dm_log > > (note, dm-mod and dm_mod are the same thing) In my case I have: # lsmod | grep dm_ dm_mirror 11678 0 dm_region_hash 9609 1 dm_mirror dm_log 8322 2 dm_mirror,dm_region_hash dm_mod 66925 8 dm_mirror,dm_log > > 5. Do an file list and make sure all the modules you need to include > (in my case the 6 in column 1): > > ls > > Note: make sure all the modules are listed ad you see the file names > (should be for me: dm-round-robin.ko, dm-multipath.ko, dm-mirror.ko, > dm-region-hash.ko, dm-log.ko, dm-mod.ko) Yes, all are present: # ls dm*.ko dm-bufio.ko dm-log-userspace.ko dm-queue-length.ko dm-service-time.ko dm-crypt.ko dm-memcache.ko dm-raid45.kodm-snapshot.ko dm-delay.ko dm-mirror.ko dm-raid.ko dm-thin-pool.ko dm-flakey.ko dm-mod.kodm-region-hash.ko dm-zero.ko dm-log.ko dm-multipath.ko dm-round-robin.ko > > 4. Create a new initrd with all the relevant md modules preloaded (in > my case, this command line ... preload only the modules you need from > your list .. again, have to do this as root): > > mkinitrd -f --preload=3Ddm_round_robin --preload=3Ddm_multipath > --preload=3Ddm_mirror --preload=3Ddm_region_hash --preload=3Ddm_log=20 > --preload=3Ddm_mod /boot/initramfs-2.6.32-358.2.1.el6.x86_64.img > 2.6.32-358.2.1.el6.x86_64 > > Note: The above mkinitrd command (and all the other commands) should be > entered all on one line, I am sure it will wrap when posted. (Indeed it did wrap.) The command I used was mkinitrd -f --preload=dm_mirror --preload=dm_region_hash --preload=dm_log --preload=dm_mod /boot/initramfs-2.6.32-358.2.1.el6.i686.img 2.6.32-358.2.1.el6.i686 That produced a file of similar size to the original: # ls -l /boot/initramfs-2.6.32-358.2.1.el6.i686.img* -rw-r--r--. 1 root root 15450686 Mar 14 15:13 /boot/initramfs-2.6.32-358.2.1.el6.i686.img -rw-r--r--. 1 root root 15450647 Mar 13 17:11 /boot/initramfs-2.6.32-358.2.1.el6.i686.img.bak > > 5. This may not work, because there may need to be some other things > loaded that are not, like the disc controller's kernel module driver, > etc. What I think is going on is either something has been removed from > this kernel that existed before ... OR ... something is being > mis-detected with this kernel on your machine. Unfortunately, when rebooting into kernel 358.2.1 I get the same result as before. Thanks for taking the time to look into this. Is it an upstream bug? -- Liam ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] moderate rant un updates
Akemi Yagi wrote: > On Thu, Mar 14, 2013 at 8:03 AM, wrote: > >> a lot of us need the proprietary driver because we use two monitors, and > *bleah* nouveau doesn't support twinview). > > Then you want to read this CentOS *FAQ*: > > http://wiki.centos.org/FAQ/CentOS6#head-012846a4e422267a34e81c4c905654fc8f36ffaf > I sure did. Last time we looked, a few years ago, it did not. When I have time, and a system to try it on (I'd really rather not disable my system for a couple hours while I play with it), I'll look into it. Thanks, Akemi. mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Kernel panic after update to 6.4
On 03/14/2013 10:33 AM, Liam O'Toole wrote: > On 2013-03-14, Johnny Hughes wrote: > > (...) > >> Maybe ... try this (everything done as root): >> >> Boot on a kernel that works and do this: >> >> 1. Backup you current initrd: >> >> cp -a /boot/initramfs-2.6.32-358.2.1.el6.x86_64.img >> /boot/initramfs-2.6.32-358.2.1.el6.x86_64.img.bak > OK. > >> 2. Go to this directory: >> >> cd /lib/modules/2.6.32-358.2.1.el6.x86_64/kernel/drivers/md/ > For me the corresponding directory is > /lib/modules/2.6.32-358.2.1.el6.i686/kernel/drivers/md. > >> 3. Figure out the md modules loaded in the old kernel: >> >> lsmod | grep dm_ >> >> in my case, that output would be this: >> >> [root@localhost md]# lsmod | grep dm_ >> dm_round_robin 2525 0 >> dm_multipath17756 1 dm_round_robin >> dm_mirror 14133 0 >> dm_region_hash 12085 1 dm_mirror >> dm_log 9930 2 dm_mirror,dm_region_hash >> dm_mod82839 12 dm_multipath,dm_mirror,dm_log >> >> (note, dm-mod and dm_mod are the same thing) > In my case I have: > > # lsmod | grep dm_ > dm_mirror 11678 0 > dm_region_hash 9609 1 dm_mirror > dm_log 8322 2 dm_mirror,dm_region_hash > dm_mod 66925 8 dm_mirror,dm_log > >> 5. Do an file list and make sure all the modules you need to include >> (in my case the 6 in column 1): >> >> ls >> >> Note: make sure all the modules are listed ad you see the file names >> (should be for me: dm-round-robin.ko, dm-multipath.ko, dm-mirror.ko, >> dm-region-hash.ko, dm-log.ko, dm-mod.ko) > Yes, all are present: > > # ls dm*.ko > dm-bufio.ko dm-log-userspace.ko dm-queue-length.ko > dm-service-time.ko > dm-crypt.ko dm-memcache.ko dm-raid45.kodm-snapshot.ko > dm-delay.ko dm-mirror.ko dm-raid.ko dm-thin-pool.ko > dm-flakey.ko dm-mod.kodm-region-hash.ko dm-zero.ko > dm-log.ko dm-multipath.ko dm-round-robin.ko > >> 4. Create a new initrd with all the relevant md modules preloaded (in >> my case, this command line ... preload only the modules you need from >> your list .. again, have to do this as root): >> >> mkinitrd -f --preload=3Ddm_round_robin --preload=3Ddm_multipath >> --preload=3Ddm_mirror --preload=3Ddm_region_hash --preload=3Ddm_log=20 >> --preload=3Ddm_mod /boot/initramfs-2.6.32-358.2.1.el6.x86_64.img >> 2.6.32-358.2.1.el6.x86_64 >> >> Note: The above mkinitrd command (and all the other commands) should be >> entered all on one line, I am sure it will wrap when posted. > (Indeed it did wrap.) The command I used was > > mkinitrd -f --preload=dm_mirror --preload=dm_region_hash > --preload=dm_log --preload=dm_mod > /boot/initramfs-2.6.32-358.2.1.el6.i686.img 2.6.32-358.2.1.el6.i686 > > That produced a file of similar size to the original: > > # ls -l /boot/initramfs-2.6.32-358.2.1.el6.i686.img* > -rw-r--r--. 1 root root 15450686 Mar 14 15:13 > /boot/initramfs-2.6.32-358.2.1.el6.i686.img > -rw-r--r--. 1 root root 15450647 Mar 13 17:11 > /boot/initramfs-2.6.32-358.2.1.el6.i686.img.bak > >> 5. This may not work, because there may need to be some other things >> loaded that are not, like the disc controller's kernel module driver, >> etc. What I think is going on is either something has been removed from >> this kernel that existed before ... OR ... something is being >> mis-detected with this kernel on your machine. > Unfortunately, when rebooting into kernel 358.2.1 I get the same result > as before. > > Thanks for taking the time to look into this. Is it an upstream bug? It is actually kind of hard to tell where the bug lies ... it is possible that somehow our kernel or other tools are causing some problem, but I would think it is more likely that some driver is not being detected and loaded. If it is in relation to dm-mod, then I would suspect that the driver is for the chipset's drive controller. If you can figure out which driver that is and make it preload, you might be able to boot ... then we can figure out why it is not detected. signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] moderate rant un updates
On 14/03/13 15:01, m.r...@5-cent.us wrote: > Johnny Hughes wrote: >> On 03/14/2013 09:17 AM, m.r...@5-cent.us wrote: >>> So, another admin I work with rolled out most (but not kernel) updates >>> to 6.4... but including xorg. I log out the end of the day, and I'm > hosed - >>> no X. > >>> I try to upgrade kmod-nvidia from elrepo. Anyone got any good >>> explanations >>> as to why they'd put kmod-nvidia-310.40 in the repo, with the previous >>> version not obvious... AND NOT HAVE THE *REQUIRED* nvidia-x11-drv-310.40 >>> in there? Why not wait until both pieces could be uploaded, since >>> kmod-nividia WILL NOT INSTALL without the other...? > >>> Also, is dkms coming in, or deprecated? >> >> None of those modules are in CentOS, but a 3rd party repo. > > That's fine. I found it annoying, but was trying to figure out whether to > set that up with the proprietary driver or not. Thanks. >> >> How about you test your setup and how 3rd party repos interact with it >> ... THEN ask on the 3rd party repo's own mailing list how or why their >> packages no longer work with the update? > > I'd Have Been Glad To Test First... but read the first para, above > > Actually, also, I note that this does *not* happen with CentOS base; I > just can't imagine why someone would do something that stupid as elrepo > seems to have. > We (elrepo) didn't. Both components were pushed together, I can assure you. Both packages were signed and pushed on 9th March, some 5 days ago. Can you please provide evidence to support your claims. Please provide a link to the mirror with the missing file then we can investigate and fix IF there is indeed an issue. Don't get me wrong - I take reports of issues very seriously. But in this case you make accusations without any evidence to support them. You don't seem interested in requesting or receiving support, but rather just want to have a rant, evidenced in part by the title of your thread and the fact you have yet to provide any useful details that would actually help someone determine what your issue is and how to best fix it. And as Johnny pointed out, this isn't even the correct forum for your rant. Anyway, I am glad to see elsewhere in this thread that you no longer intend to use the elrepo NVIDIA packages. I am glad you have found a solution that works for you and wish you good luck with that. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] moderate rant un updates
Ned Slider wrote: > On 14/03/13 15:01, m.r...@5-cent.us wrote: >> Johnny Hughes wrote: >>> On 03/14/2013 09:17 AM, m.r...@5-cent.us wrote: So, another admin I work with rolled out most (but not kernel) updates to 6.4... but including xorg. I log out the end of the day, and I'm >> hosed - no X. >> I try to upgrade kmod-nvidia from elrepo. Anyone got any good explanations as to why they'd put kmod-nvidia-310.40 in the repo, with the previous version not obvious... AND NOT HAVE THE *REQUIRED* nvidia-x11-drv-310.40 in there? Why not wait until both pieces could be uploaded, since kmod-nividia WILL NOT INSTALL without the other...? > We (elrepo) didn't. Both components were pushed together, I can assure > you. Both packages were signed and pushed on 9th March, some 5 days ago. > > Can you please provide evidence to support your claims. Please provide a > link to the mirror with the missing file then we can investigate and fix > IF there is indeed an issue. yum install kmod-nvidia nvidia-x11-drv --disablerepo=\* --enablerepo=elrepo Loaded plugins: fastestmirror, presto, ps, security Loading mirror speeds from cached hostfile * elrepo: mirror.symnds.com Setting up Install Process No package nvidia-x11-drv available. Resolving Dependencies --> Running transaction check ---> Package kmod-nvidia.x86_64 0:310.40-1.el6.elrepo will be installed --> Processing Dependency: nvidia-x11-drv = 310.40 for package: kmod-nvidia-310.40-1.el6.elrepo.x86_64 --> Finished Dependency Resolution Error: Package: kmod-nvidia-310.40-1.el6.elrepo.x86_64 (elrepo) Requires: nvidia-x11-drv = 310.40 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest > > Anyway, I am glad to see elsewhere in this thread that you no longer > intend to use the elrepo NVIDIA packages. I am glad you have found a > solution that works for you and wish you good luck with that. Obviously, you didn't read it closely. I found a solution to get me back to work. I strongly preferred the kmod-nvidia, since it does not require me to manually build the drivers every time I upgrade the kernel, and I have a number of users I support with similar issues. mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] moderate rant un updates
On 14/03/13 16:34, m.r...@5-cent.us wrote: > Ned Slider wrote: >> On 14/03/13 15:01, m.r...@5-cent.us wrote: >>> Johnny Hughes wrote: On 03/14/2013 09:17 AM, m.r...@5-cent.us wrote: > So, another admin I work with rolled out most (but not kernel) updates > to 6.4... but including xorg. I log out the end of the day, and I'm >>> hosed - no X. >>> > I try to upgrade kmod-nvidia from elrepo. Anyone got any good > explanations as to why they'd put kmod-nvidia-310.40 in the repo, with > the previous version not obvious... AND NOT HAVE THE *REQUIRED* > nvidia-x11-drv-310.40 in there? Why not wait until both pieces could be > uploaded, since kmod-nividia WILL NOT INSTALL without the other...? > >> We (elrepo) didn't. Both components were pushed together, I can assure >> you. Both packages were signed and pushed on 9th March, some 5 days ago. >> >> Can you please provide evidence to support your claims. Please provide a >> link to the mirror with the missing file then we can investigate and fix >> IF there is indeed an issue. > > yum install kmod-nvidia nvidia-x11-drv --disablerepo=\* --enablerepo=elrepo > Loaded plugins: fastestmirror, presto, ps, security > Loading mirror speeds from cached hostfile > * elrepo: mirror.symnds.com > Setting up Install Process > No package nvidia-x11-drv available. > Resolving Dependencies > --> Running transaction check > ---> Package kmod-nvidia.x86_64 0:310.40-1.el6.elrepo will be installed > --> Processing Dependency: nvidia-x11-drv = 310.40 for package: > kmod-nvidia-310.40-1.el6.elrepo.x86_64 > --> Finished Dependency Resolution > Error: Package: kmod-nvidia-310.40-1.el6.elrepo.x86_64 (elrepo) > Requires: nvidia-x11-drv = 310.40 > You could try using --skip-broken to work around the problem > You could try running: rpm -Va --nofiles --nodigest > The package is there on that mirror: http://mirror.symnds.com/distributions/elrepo/elrepo/el6/x86_64/RPMS/nvidia-x11-drv-310.40-1.el6.elrepo.x86_64.rpm which means the issue is your end. Please show your /etc/yum.repos.d/elrepo.repo ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] moderate rant un updates
On Thu, Mar 14, 2013 at 10:01 AM, Ned Slider wrote: > On 14/03/13 16:34, m.r...@5-cent.us wrote: >> yum install kmod-nvidia nvidia-x11-drv --disablerepo=\* --enablerepo=elrepo >> Loaded plugins: fastestmirror, presto, ps, security >> Loading mirror speeds from cached hostfile >> * elrepo: mirror.symnds.com >> Setting up Install Process >> No package nvidia-x11-drv available. >> Resolving Dependencies >> --> Running transaction check >> ---> Package kmod-nvidia.x86_64 0:310.40-1.el6.elrepo will be installed >> --> Processing Dependency: nvidia-x11-drv = 310.40 for package: >> kmod-nvidia-310.40-1.el6.elrepo.x86_64 >> --> Finished Dependency Resolution >> Error: Package: kmod-nvidia-310.40-1.el6.elrepo.x86_64 (elrepo) >> Requires: nvidia-x11-drv = 310.40 >> You could try using --skip-broken to work around the problem >> You could try running: rpm -Va --nofiles --nodigest >> > > The package is there on that mirror: > > http://mirror.symnds.com/distributions/elrepo/elrepo/el6/x86_64/RPMS/nvidia-x11-drv-310.40-1.el6.elrepo.x86_64.rpm > > which means the issue is your end. > > Please show your /etc/yum.repos.d/elrepo.repo Also check your exclude= line(s). Akemi ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] SOLUTION: Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller - GDM login doesn't show up
On Thu, 14 Mar 2013 16:24:45 +0400 Andreas K. wrote: > I have loaded CentOS 5.x on an Intel D525 CPU (I believe) motherboard a > while > back and no such "special" treatment was required. Are you sure that > this is not > just a specific problem with the box you are using? Since I have two identical machines that both exhibit the same problem (with two different models/sizes of monitors attached -- one newish Acer widescreen monitor and one older Benq 17" monitor) I'm pretty sure it's not just a specific problem with one box or one monitor or combination thereof. Now that I know the fix, it's easy enough to do and of course I've made notes to guide myself if this situation arises again. -- MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com www.creekfm.com - FIFTY THOUSAND WATTS of POW WOW POWER! ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Using LAMP stacks
> >Your server has probably got all the components of a LAMP stack on it. >If it hasn't it is a simple matter of installing them using yum. You would learn a lot by doing it that way. yum will put stuff in the correct locations. >If you are sure that you want to use a pre-packed LAMP stack, then I guess that they must use different ports. I've never used one. I suspect that you will have issues >down the track, eg when you need to upgrade either the system or the LAMP stack. >One option is to find an appliance ISO and use that rather than try to install a LAMP stack on top of an existing system. I suppose you are correct. The real problem I was having was getting domain1.com to point to one location and domain2.com to point to another and to serve php files from both. Previously, I had problems with this, especially frustrating was when php didn't work. Didn't work meaning it wasn't being processed on the server. With my latest install that does work now. It was s frustrating. Nothing out there seemed to offer a solution and the log files were unhelpful. These packaged lamp stacks do not resolve the issue of running virtual domains, such as domain1.com and domain2.com. As noted in a prior email, when I added a vhost.conf file, the server would not restart. Thanks, Bruce ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Mounting USB drives read-only by default?
Try to edit /etc/fstat Sometimes this is the only way On Mar 14, 2013 10:34 AM, "James Pearson" wrote: > Is it possible to configure the automounting of USB drives to mount > read-only? > > Is there some gconf/udev/udisks/hal/whatever setting to alter the > default mount options when USB disks are plugged in by users? > > Thanks > > James Pearson > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Using LAMP stacks
Bruce Whealton wrote: >>One option is to find an appliance ISO and use that rather than try to > install a LAMP stack on top of an existing system. > > I suppose you are correct. The real problem I was having was getting > domain1.com to point to one location and domain2.com to point to another > and to serve php files from both. Previously, I had problems with this, > especially frustrating was when php didn't work. Didn't work meaning it > wasn't being processed on the server. With my latest install that does > work now. It was s frustrating. Nothing out there seemed to offer a > solution and the log files were unhelpful. > These packaged lamp stacks do not resolve the issue of running virtual > domains, such as domain1.com and domain2.com. As noted in a prior email, > when I added a vhost.conf file, the server would not restart. You should note that current practice is to touch /etc/httpd/conf as *little* as possible. It includes /etc/httpd/conf.d, and in there, you put your files. What most people do is one for each domain. mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Vhost.conf file and info. re: partitions and physical drives
I had to go to /home/www/futurewavewebdevelopment.com/logs and in the error log, it just says that access is forbidden. I changed the permissions and ownership to apache:apache which is what was working before. If I remove that, I can get to the default page at /var/html/www and it displays my new test page and the php. Then I tried to have the vhost.conf file point to a directory underneath where the default location is in the /etc/httpd/conf/httpd.conf file - that is /var/www/html So, I changed the /home below to be /var and I created the respective directories, such as /var/www/futurewavewebdevelopment.com/public_html which is what I used in the /etc/httpd/conf.d/vhost.conf file. Now, the server won't restart. Maybe I need to put the errors into a pastbin and see if that helps. What I see does not help. Any ideas, Bruce > > thanks in advance for help. I'll post the vhost.conf file that caused > the server to not start. > > NameVirtualHost *:80 > > > ServerAdmin webmas...@fwwebdev.dnsdynamic.com > ServerName fwwebdev.dnsdynamic.com > ServerAlias www.fwwebdev.dnsdynamic.com > DocumentRoot /home/www/fwwebdev.dnsdynamic.com/public_html/ > ErrorLog /home/www/fwwebdev.dnsdynamic.com/logs/error.log > CustomLog /home/www/fwwebdev.dnsdynamic.com/logs/access.log > combined > > > ServerAdmin webmas...@futurewavewebdevelopment.com > ServerName futurewavewebdevelopment.com > ServerAlias www.futurewavewebdevelopment.com > DocumentRoot /home/www/futurewavewebdevelopment.com/public_html/ > ErrorLog /home/www/futurewavewebdevelopment.com/logs/error.log > CustomLog /home/www/futurewavewebdevelopment.com/logs/access.log > combined > > > > Bruce > > > ___ > Bruce Whealton - Web Design/Development/Programming Future Wave Web > Development: > http://futurewaveonline.com > Developing for the Desktop as well as for Mobile Devices - > Smartphones/Tablets Call 919-636-5809 > ___ > > > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > -- ---~~.~~--- Mike // SilverTip257 // ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Vhost.conf file and info. re: partitions and physical drives
Bruce Whealton wrote: > I had to go to /home/www/futurewavewebdevelopment.com/logs > and in the error log, it just says that access is forbidden. I changed the > permissions and ownership to apache:apache which is what was working > before. > If I remove that, I can get to the default page at /var/html/www and it > displays my new test page and the php. > Then I tried to have the vhost.conf file point to a directory underneath > where the default location is in the /etc/httpd/conf/httpd.conf file - > that is /var/www/html > So, I changed the /home below to be /var and I created the respective > directories, such as /var/www/futurewavewebdevelopment.com/public_html > which is what I used in the /etc/httpd/conf.d/vhost.conf file. > Now, the server won't restart. > Maybe I need to put the errors into a pastbin and see if that helps. > What I see does not help. > Any ideas, What's the DirectoryRoot? Really, what's more common is /var/www/html (or whatever your company's practice is, and under *that* /var/www/html/mydomain1.com /var/www/html/mydomain2.com etc., with /var/www/html the overriding DirectoryRoot, but only /var/www/html/mydomain1.com as DirectoryRoot in each of the configuration files, /etc/httpd/conf.d/mydomain1.conf, etc. mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Vhost.conf file and info. re: partitions and physical drives
Oh, yes - what are the permissions on /etc/httpd/conf and /etc/httpd/conf.d? mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Vhost.conf file and info. re: partitions and physical drives
On Thu, Mar 14, 2013 at 2:00 PM, wrote: > Oh, yes - what are the permissions on /etc/httpd/conf and /etc/httpd/conf.d? > And if selinux is enabled, do you see denials in /var/log/audit/audit.log for the files in question? -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] moderate rant un updates
This may be slightly off topic on this thread but on all my workstations using the Nvidia kmod from elrepo, the update to xorg removed the symbolic link 'libglx.so in /usr/lib64/xorg/modules/extensions/nvidia that points to nvidia's libglx.so.304.64. Restoring that symbolic link restored normal operation. Perhaps a 'yum --enablerepo=elrepo reinstall kmod-nvidia' would have accomplished the same thing but did not try it. Seems like it might not be the elrepo package that is the probleb. B.J. CentOS release 6.4 (Final) On Thu, 2013-03-14 at 09:25 -0500, Johnny Hughes wrote: > On 03/14/2013 09:17 AM, m.r...@5-cent.us wrote: > > So, another admin I work with rolled out most (but not kernel) updates to > > 6.4... but including xorg. I log out the end of the day, and I'm hosed - > > no X. > > > > Now, my not-two-year-old workstation has an nvidia card, and I'd installed > > kmod-nvidia from elrepo. I figured I'd fix my problem by finishing the > > upgrade and rebooting. > > > > Nope. > > > > I try to upgrade kmod-nvidia from elrepo. Anyone got any good explanations > > as to why they'd put kmod-nvidia-310.40 in the repo, with the previous > > version not obvious... AND NOT HAVE THE *REQUIRED* nvidia-x11-drv-310.40 > > in there? Why not wait until both pieces could be uploaded, since > > kmod-nividia WILL NOT INSTALL without the other...? > > > > I then stupidly uninstalled the previous kmod-nvidia & nvidia-x11-drv, > > hoping it would allow a good install. > > > > Nope. > > > > Found the proprietary installer on the NVidia site, and I'm up. > > > > > > On a related note, does anyone have a link to a howto build the NVidia > > proprietary driver on a kernel that's *not* running, so we could prebuild > > it before the reboot? I see there are options in the script, but no > > examples. > > > > Also, is dkms coming in, or deprecated? > > None of those modules are in CentOS, but a 3rd party repo. > > How about you test your setup and how 3rd party repos interact with it > ... THEN ask on the 3rd party repo's own mailing list how or why their > packages no longer work with the update? > > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] moderate rant un updates
Akemi Yagi wrote: > On Thu, Mar 14, 2013 at 10:01 AM, Ned Slider wrote: >> On 14/03/13 16:34, m.r...@5-cent.us wrote: > >>> yum install kmod-nvidia nvidia-x11-drv --disablerepo=\* >>> --enablerepo=elrepo >>> Loaded plugins: fastestmirror, presto, ps, security >>> Loading mirror speeds from cached hostfile >>> * elrepo: mirror.symnds.com >>> Setting up Install Process >>> No package nvidia-x11-drv available. >>> Resolving Dependencies >>> --> Running transaction check >>> ---> Package kmod-nvidia.x86_64 0:310.40-1.el6.elrepo will be installed >>> --> Processing Dependency: nvidia-x11-drv = 310.40 for package: >>> kmod-nvidia-310.40-1.el6.elrepo.x86_64 >>> --> Finished Dependency Resolution >>> Error: Package: kmod-nvidia-310.40-1.el6.elrepo.x86_64 (elrepo) >>> Requires: nvidia-x11-drv = 310.40 >>> You could try using --skip-broken to work around the problem >>> You could try running: rpm -Va --nofiles --nodigest >> >> The package is there on that mirror: >> >> http://mirror.symnds.com/distributions/elrepo/elrepo/el6/x86_64/RPMS/nvidia-x11-drv-310.40-1.el6.elrepo.x86_64.rpm >> >> which means the issue is your end. >> >> Please show your /etc/yum.repos.d/elrepo.repo > > Also check your exclude= line(s). Thanks, both of you, and good catch. Now I need to dig into what happened on *my* end: the elrepo.conf was dated last summer, and I had kmod-nvidia and nvidia-x11-drv installed... but when you folks pointed me to it, it *only* had includepkgs=kmod-nvidia. I know I didn't do a localinstall, so I need to figure out how I installed it, if the repo file was like that, or if it got backed up to some in-progress repo from before I got the install working. mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] moderate rant un updates
On Thu, Mar 14, 2013 at 12:43 PM, wrote: > Thanks, both of you, and good catch. Now I need to dig into what happened > on *my* end: the elrepo.conf was dated last summer, and I had kmod-nvidia > and nvidia-x11-drv installed... but when you folks pointed me to it, it > *only* had includepkgs=kmod-nvidia. I know I didn't do a localinstall, so > I need to figure out how I installed it, if the repo file was like that, > or if it got backed up to some in-progress repo from before I got the > install working. > > mark So, what you've found is that this is a recurrence of the old problem you had before? http://lists.centos.org/pipermail/centos/2012-July/127950.html If so, just curious why this resurfaced. Akemi ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] moderate rant un updates
Akemi Yagi wrote: > On Thu, Mar 14, 2013 at 12:43 PM, wrote: > >> Thanks, both of you, and good catch. Now I need to dig into what >> happened on *my* end: the elrepo.conf was dated last summer, and I had >> kmod-nvidia and nvidia-x11-drv installed... but when you folks pointed me to it, it >> *only* had includepkgs=kmod-nvidia. I know I didn't do a localinstall, >> so I need to figure out how I installed it, if the repo file was like that, >> or if it got backed up to some in-progress repo from before I got the >> install working. > > So, what you've found is that this is a recurrence of the old problem > you had before? > > http://lists.centos.org/pipermail/centos/2012-July/127950.html > > If so, just curious why this resurfaced. I'd forgotten about that, but yep, that's it. Hmmm... thank you I think, I see it now: that was *right* around the time that I got this workstation, and was building it. Wonder if I explicitly, on a command line, got that, and then didn't add it, or whether this got restored from something during that initial build I'll make sure *that* doesn't happen again. Again, thanks to all who helped me pinpoint what went wrong. I'm still ticked at the other admin who pushed me into this, rather than waiting for me to walk through it step by step mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] cgroups not working?
On Wed, Mar 13, 2013 at 10:10 PM, Dennis Jacobfeuerborn
wrote:
> Hi,
> I'm trying to use cgroups to limit the apache webserver but this doesn't
> seem to work as far as I can tell.
> I modified cgconfig.conf like this:
>
> group webserver {
> cpu {
> cpu.shares="250";
> }
> }
How many other groups do you have defined? IIRC, it was based on the
ratio of that share to the total. So if that's the only group defined,
it may end up getting all resources.
http://hydra.geht.net/tino/english/faq/debian/squeeze/cgroups/
This seems to indicate that is how it works..
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Using LAMP stacks
On Fri, Mar 15, 2013 at 6:53 AM, Bruce Whealton wrote: >> >>Your server has probably got all the components of a LAMP stack on it. >>If it hasn't it is a simple matter of installing them using yum. You would > learn a lot by doing it that way. yum will put stuff in the correct > locations. > >>If you are sure that you want to use a pre-packed LAMP stack, then I guess > that they must use different ports. I've never used one. I suspect that you > will have issues >down the track, eg when you need to upgrade either the > system or the LAMP stack. > >>One option is to find an appliance ISO and use that rather than try to > install a LAMP stack on top of an existing system. > > I suppose you are correct. The real problem I was having was getting > domain1.com to point to one location and domain2.com to point to another and > to serve php files from both. Previously, I had problems with this, > especially frustrating was when php didn't work. Didn't work meaning it > wasn't being processed on the server. With my latest install that does work > now. It was s frustrating. Nothing out there seemed to offer a > solution and the log files were unhelpful. > These packaged lamp stacks do not resolve the issue of running virtual > domains, such as domain1.com and domain2.com. As noted in a prior email, > when I added a vhost.conf file, the server would not restart. > Thanks, > I suggest that solving the issues that you get would be ultimately more useful than looking for a solution that works out of the box. I suggest that you look at the documentation for Apache virtual hosts. Cheers, Cliff ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] atheros wifi on my oqo2
On Thu, Mar 14, 2013 at 4:27 PM, Robert Moskowitz wrote: Ugh I clicked reply rather than reply-all on your message that was also sent directly to me. Back on the list we go. :) > On 03/14/2013 12:33 PM, SilverTip257 wrote: > > On Wed, Mar 13, 2013 at 9:53 PM, Robert Moskowitz wrote: > >> >> On 03/13/2013 11:17 AM, SilverTip257 wrote: >> >>> On Wed, Mar 13, 2013 at 9:48 AM, Robert Moskowitz >> >wrote: >>> >>> I have a few oqo2 units that I use for testing, normally using the dongle for ethernet connection. Well supposedly they have atheros wifi. in dmseg I see: >>> OT: Looks like a pretty neat device. http://www.youtube.com/watch?v=gt84OKzFQis > ath5k :03:04.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 ath5k :03:04.0: registered as 'phy0' ath5k phy0: Couldn't identify radio revision. ath5k :03:04.0: PCI INT A disabled I press magic per http://www.expansys.com/ft.aspx?k=119902 but NetworkManager is not adding wifi as a networking device. There is no file under /etc/sysconfig/network-scripts/ifc-* either. How can I get the wifi working? Does the Atheros device show up in the output of ifconfig? >>> ifconfig -a >>> >> >> Only eth0 and lo >> >> >> If it does, check the output of iwconfig. >>> >> >> And of course nothing here. >> >> If neither of those yield any success, dig into the output of lspci for >>> info on the Ath device. >>> lspci -v >>> lspci -v | grep -A10 -B2 thernet >>> >>> with verbosity turne up another notch if you want more info >>> lspci -vv | grep -A10 -B2 thernet >>> >> >> # lspci -vv | grep -A10 -B2 thernet >> Kernel modules: snd-hda-intel >> >> 03:04.0 Ethernet controller: Atheros Communications Inc. AR5413/AR5414 >> Wireless Network Adapter [AR5006X(S) 802.11abg] (rev 01) >> > > What version of CentOS? 6.4? > > > Still 6.3. I am going to rebuild on one of them tomorrow (or maybe > tonight) to 6.4. > > You might try an install of Fedora instead (as I suggest at the bottom of this message) and try a newer kernel. Maybe you'll end up using the CentOS base and need to build a newer kernel yourself to have the proper driver for that Atheros chip. Since that unit will probably not be an Internet-facing host, you can run a custom kernel without any drawbacks. Since CentOS 6.[34] is running a 2.6.32 kernel, I don't know that I place much belief in this information [0] (see post #4) helping. And this poster's Atheros is an AR5001. [0] http://ubuntuforums.org/showthread.php?t=1350358&p=8475659 > > > By chance have you tried probing the driver by manually to test? > modprobe ath5k > lsmod | grep ath > > > ath5k 129334 0 > ath14106 1 ath5k > mac80211 184028 1 ath5k > cfg80211 157313 3 ath5k,ath,mac80211 > > ifconfig -a > > > And still only eth0 and lo listed. > > I looked into messages and picked out the following: > > Mar 11 01:37:17 oqo2 kernel: ath5k :03:04.0: PCI INT A -> GSI 17 > (level, low) -> IRQ 17 > Mar 11 01:37:17 oqo2 kernel: ath5k :03:04.0: registered as 'phy0' > Mar 11 01:37:17 oqo2 kernel: ath5k phy0: Couldn't identify radio revision. > Mar 11 01:37:17 oqo2 kernel: ath5k :03:04.0: PCI INT A disabled > > Perhaps this is my problem? > > Yes. > > > You might also try the tips listed here: > http://wiki.centos.org/HowTos/Laptops/Wireless > > > Nothing helpful there. ath5k should just work. > > Agreed. You may end up checking change logs for kernel versions. :-/ > > > Check modprobe's blacklist config for kicks. > > Being an Atheros card I'd expect it to be rather well supported. > > >> Subsystem: Atheros Communications Inc. EnGenius EMP-8602 (400mw) or >> Compex WLM54AG (SuperAG) >> Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- >> Stepping- SERR- FastB2B- DisINTx- >> Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- >> SERR- > Interrupt: pin A routed to IRQ 17 >> Region 0: Memory at c210 (32-bit, non-prefetchable) [size=64K] >> Capabilities: [44] Power Management version 2 >> Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA >> PME(D0-,D1-,D2-,D3hot-,D3cold-) >> Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=2 PME- >> Kernel modules: ath5k >> >> 03:05.0 Ethernet controller: Realtek Semiconductor Co., Ltd. >> RTL-8139/8139C/8139C+ (rev 10) >> Subsystem: Atheros Communications Inc. Device 8139 >> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- >> Stepping- SERR- FastB2B- DisINTx- >> Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- >> SERR- > Latency: 32 (8000ns min, 16000ns max) >> Interrupt: pin A routed to IRQ 18 >> Region 0: I/O ports at bc00 [size=256] >> Region 1: Memory at c211 (32-bit, non-prefetchable) [size=256] >> Capabilities: [50] Power Management version 2 >> Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA >> PME(D0-,D1+
[CentOS] Postfix/Amavisd/Clamd - Mail send failing
Dear All
With help from you all I am now at better stage. Special thanks to Robert.
Atleast I am able to run all the required services (postfix, amavisd, clamd
etc).
I sent a mail from my gmail, I received at my newly setup domain/mailbox.
I am facing issue while sending the mail outside.
>From maillog I realized, two issues are there.
*1. Virus scan failed. The error log is as below *
*Mar 14 18:49:55 ip-173-201-189-43 amavis[3325]: (03325-01) (!)run_av
(ClamAV-clamd) FAILED - unexpected ,
output="/var/spool/amavisd/tmp/amavis-20130314T184955-03325-nFS5UJ4F/parts:
lstat() failed: Permission denied. ERROR\n"
Mar 14 18:49:55 ip-173-201-189-43 amavis[3325]: (03325-01) (!)ClamAV-clamd
av-scanner FAILED: CODE(0x19c3ec0) unexpected ,
output="/var/spool/amavisd/tmp/amavis-20130314T184955-03325-nFS5UJ4F/parts:
lstat() failed: Permission denied. ERROR\n" at (eval 113) line 897.
Mar 14 18:49:55 ip-173-201-189-43 amavis[3325]: (03325-01) (!)WARN: all
primary virus scanners failed, considering backups
*
*2. Looks destination network not reachable (probably here gmail's mail
server)*
*
Mar 14 18:49:58 ip-173-201-189-43 amavis[3325]: (03325-01) FWD from <
bh...@netcloudjobs.com> -> ,BODY=7BIT 250 2.0.0
from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 1AE0E38A0D3E
Mar 14 18:49:58 ip-173-201-189-43 postfix/error[3384]: 1AE0E38A0D3E: to=<
austin.ein...@gmail.com>, relay=none, delay=0.02, delays=0.01/0.01/0/0,
dsn=4.4.1, status=deferred (delivery temporarily suspended: connect to
alt2.gmail-smtp-in.l.google.com[2607:f8b0:4002:c04::1a]:25: Network is
unreachable)
Mar 14 18:49:58 ip-173-201-189-43 amavis[3325]: (03325-01) Passed CLEAN
{RelayedOutbound}, MYNETS LOCAL [127.0.0.1]:46504 [127.0.0.1] <
bh...@netcloudjobs.com> -> , Message-ID: <
bd17726f3d35c7980426e4a55566c...@netcloudjobs.com>, mail_id: T8Zt2QE1Eico,
Hits: -1, size: 805, queued_as: 1AE0E38A0D3E, 2885 ms
*
Is it a dns issue. Why my mail server is saying "*delivery temporarily
suspended: connect to
alt2.gmail-smtp-in.l.google.com[2607:f8b0:4002:c04::1a]:25:
Network is unreachable)*".
Kindly guide me to solve these 2 issues.
Best regards
Austin
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Postfix/Amavisd/Clamd - Mail send failing
I hope I have solved the first issue by giving right permission to
/var/spool/amavisd/tmp.
I gave the permission to that folder as 770.
Any input for 2nd issue.., Can it be a firewall issue, do I need to
open any port in IN or OUT interfaces...
It is strange when it logs "*very temporarily suspended: connect to
alt2.gmail-smtp-in.l.google.com[2607:f8b0:4002:c04::1a]:25: Network is
unreachable*".
It is just some network/dns setting causing the issue, not able to catch
the issue here .., any input...
-Austin
On Fri, Mar 15, 2013 at 7:38 AM, Austin Einter wrote:
> Dear All
> With help from you all I am now at better stage. Special thanks to Robert.
>
> Atleast I am able to run all the required services (postfix, amavisd,
> clamd etc).
>
> I sent a mail from my gmail, I received at my newly setup domain/mailbox.
>
> I am facing issue while sending the mail outside.
>
> From maillog I realized, two issues are there.
>
>
> *1. Virus scan failed. The error log is as below *
>
> *Mar 14 18:49:55 ip-173-201-189-43 amavis[3325]: (03325-01) (!)run_av
> (ClamAV-clamd) FAILED - unexpected ,
> output="/var/spool/amavisd/tmp/amavis-20130314T184955-03325-nFS5UJ4F/parts:
> lstat() failed: Permission denied. ERROR\n"
> Mar 14 18:49:55 ip-173-201-189-43 amavis[3325]: (03325-01) (!)ClamAV-clamd
> av-scanner FAILED: CODE(0x19c3ec0) unexpected ,
> output="/var/spool/amavisd/tmp/amavis-20130314T184955-03325-nFS5UJ4F/parts:
> lstat() failed: Permission denied. ERROR\n" at (eval 113) line 897.
> Mar 14 18:49:55 ip-173-201-189-43 amavis[3325]: (03325-01) (!)WARN: all
> primary virus scanners failed, considering backups
> *
>
> *2. Looks destination network not reachable (probably here gmail's mail
> server)*
> *
> Mar 14 18:49:58 ip-173-201-189-43 amavis[3325]: (03325-01) FWD from <
> bh...@netcloudjobs.com> -> ,BODY=7BIT 250 2.0.0
> from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 1AE0E38A0D3E
> Mar 14 18:49:58 ip-173-201-189-43 postfix/error[3384]: 1AE0E38A0D3E: to=<
> austin.ein...@gmail.com>, relay=none, delay=0.02, delays=0.01/0.01/0/0,
> dsn=4.4.1, status=deferred (delivery temporarily suspended: connect to
> alt2.gmail-smtp-in.l.google.com[2607:f8b0:4002:c04::1a]:25: Network is
> unreachable)
> Mar 14 18:49:58 ip-173-201-189-43 amavis[3325]: (03325-01) Passed CLEAN
> {RelayedOutbound}, MYNETS LOCAL [127.0.0.1]:46504 [127.0.0.1] <
> bh...@netcloudjobs.com> -> , Message-ID: <
> bd17726f3d35c7980426e4a55566c...@netcloudjobs.com>, mail_id:
> T8Zt2QE1Eico, Hits: -1, size: 805, queued_as: 1AE0E38A0D3E, 2885 ms
> *
> Is it a dns issue. Why my mail server is saying "*delivery temporarily
> suspended: connect to
> alt2.gmail-smtp-in.l.google.com[2607:f8b0:4002:c04::1a]:25:
> Network is unreachable)*".
>
> Kindly guide me to solve these 2 issues.
>
> Best regards
> Austin
>
>
>
>
>
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Postfix/Amavisd/Clamd - Mail send failing
I just executed below command
*[root@ip-173-201-189-43 tmp]#
[root@ip-173-201-189-43 tmp]# telnet gmail-smtp-in.l.google.com 25
Trying 173.194.79.27...
telnet: connect to address 173.194.79.27: No route to host
Trying 2607:f8b0:400e:c01::1b...
telnet: connect to address 2607:f8b0:400e:c01::1b: Network is unreachable
[root@ip-173-201-189-43 tmp]#
*
Looks its a generic issue, nothing to do with mail setup.
I am not able to connect to gmail server's 25 port.
What is the work around here, any idea.
On Fri, Mar 15, 2013 at 8:38 AM, Austin Einter wrote:
> I hope I have solved the first issue by giving right permission to
> /var/spool/amavisd/tmp.
> I gave the permission to that folder as 770.
>
> Any input for 2nd issue.., Can it be a firewall issue, do I need to
> open any port in IN or OUT interfaces...
>
> It is strange when it logs "*very temporarily suspended: connect to
> alt2.gmail-smtp-in.l.google.com[2607:f8b0:4002:c04::1a]:25: Network is
> unreachable*".
>
> It is just some network/dns setting causing the issue, not able to catch
> the issue here .., any input...
>
> -Austin
>
>
>
> On Fri, Mar 15, 2013 at 7:38 AM, Austin Einter wrote:
>
>> Dear All
>> With help from you all I am now at better stage. Special thanks to Robert.
>>
>> Atleast I am able to run all the required services (postfix, amavisd,
>> clamd etc).
>>
>> I sent a mail from my gmail, I received at my newly setup domain/mailbox.
>>
>> I am facing issue while sending the mail outside.
>>
>> From maillog I realized, two issues are there.
>>
>>
>> *1. Virus scan failed. The error log is as below *
>>
>> *Mar 14 18:49:55 ip-173-201-189-43 amavis[3325]: (03325-01) (!)run_av
>> (ClamAV-clamd) FAILED - unexpected ,
>> output="/var/spool/amavisd/tmp/amavis-20130314T184955-03325-nFS5UJ4F/parts:
>> lstat() failed: Permission denied. ERROR\n"
>> Mar 14 18:49:55 ip-173-201-189-43 amavis[3325]: (03325-01)
>> (!)ClamAV-clamd av-scanner FAILED: CODE(0x19c3ec0) unexpected ,
>> output="/var/spool/amavisd/tmp/amavis-20130314T184955-03325-nFS5UJ4F/parts:
>> lstat() failed: Permission denied. ERROR\n" at (eval 113) line 897.
>> Mar 14 18:49:55 ip-173-201-189-43 amavis[3325]: (03325-01) (!)WARN: all
>> primary virus scanners failed, considering backups
>> *
>>
>> *2. Looks destination network not reachable (probably here gmail's mail
>> server)*
>> *
>> Mar 14 18:49:58 ip-173-201-189-43 amavis[3325]: (03325-01) FWD from <
>> bh...@netcloudjobs.com> -> ,BODY=7BIT 250 2.0.0
>> from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 1AE0E38A0D3E
>> Mar 14 18:49:58 ip-173-201-189-43 postfix/error[3384]: 1AE0E38A0D3E: to=<
>> austin.ein...@gmail.com>, relay=none, delay=0.02, delays=0.01/0.01/0/0,
>> dsn=4.4.1, status=deferred (delivery temporarily suspended: connect to
>> alt2.gmail-smtp-in.l.google.com[2607:f8b0:4002:c04::1a]:25: Network is
>> unreachable)
>> Mar 14 18:49:58 ip-173-201-189-43 amavis[3325]: (03325-01) Passed CLEAN
>> {RelayedOutbound}, MYNETS LOCAL [127.0.0.1]:46504 [127.0.0.1] <
>> bh...@netcloudjobs.com> -> , Message-ID: <
>> bd17726f3d35c7980426e4a55566c...@netcloudjobs.com>, mail_id:
>> T8Zt2QE1Eico, Hits: -1, size: 805, queued_as: 1AE0E38A0D3E, 2885 ms
>> *
>> Is it a dns issue. Why my mail server is saying "*delivery temporarily
>> suspended: connect to
>> alt2.gmail-smtp-in.l.google.com[2607:f8b0:4002:c04::1a]:25:
>> Network is unreachable)*".
>>
>> Kindly guide me to solve these 2 issues.
>>
>> Best regards
>> Austin
>>
>>
>>
>>
>>
>
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Postfix/Amavisd/Clamd - Mail send failing
I just checked firewall. tcp/smtp(25 ) is allowed.
Any kind of DNS configuration issues
Any pointers .
On Fri, Mar 15, 2013 at 8:50 AM, Austin Einter wrote:
> I just executed below command
>
> *[root@ip-173-201-189-43 tmp]#
> [root@ip-173-201-189-43 tmp]# telnet gmail-smtp-in.l.google.com 25
> Trying 173.194.79.27...
> telnet: connect to address 173.194.79.27: No route to host
> Trying 2607:f8b0:400e:c01::1b...
> telnet: connect to address 2607:f8b0:400e:c01::1b: Network is unreachable
> [root@ip-173-201-189-43 tmp]#
> *
> Looks its a generic issue, nothing to do with mail setup.
>
> I am not able to connect to gmail server's 25 port.
>
> What is the work around here, any idea.
>
>
>
>
>
> On Fri, Mar 15, 2013 at 8:38 AM, Austin Einter wrote:
>
>> I hope I have solved the first issue by giving right permission to
>> /var/spool/amavisd/tmp.
>> I gave the permission to that folder as 770.
>>
>> Any input for 2nd issue.., Can it be a firewall issue, do I need to
>> open any port in IN or OUT interfaces...
>>
>> It is strange when it logs "*very temporarily suspended: connect to
>> alt2.gmail-smtp-in.l.google.com[2607:f8b0:4002:c04::1a]:25: Network is
>> unreachable*".
>>
>> It is just some network/dns setting causing the issue, not able to catch
>> the issue here .., any input...
>>
>> -Austin
>>
>>
>>
>> On Fri, Mar 15, 2013 at 7:38 AM, Austin Einter
>> wrote:
>>
>>> Dear All
>>> With help from you all I am now at better stage. Special thanks to
>>> Robert.
>>>
>>> Atleast I am able to run all the required services (postfix, amavisd,
>>> clamd etc).
>>>
>>> I sent a mail from my gmail, I received at my newly setup domain/mailbox.
>>>
>>> I am facing issue while sending the mail outside.
>>>
>>> From maillog I realized, two issues are there.
>>>
>>>
>>> *1. Virus scan failed. The error log is as below *
>>>
>>> *Mar 14 18:49:55 ip-173-201-189-43 amavis[3325]: (03325-01) (!)run_av
>>> (ClamAV-clamd) FAILED - unexpected ,
>>> output="/var/spool/amavisd/tmp/amavis-20130314T184955-03325-nFS5UJ4F/parts:
>>> lstat() failed: Permission denied. ERROR\n"
>>> Mar 14 18:49:55 ip-173-201-189-43 amavis[3325]: (03325-01)
>>> (!)ClamAV-clamd av-scanner FAILED: CODE(0x19c3ec0) unexpected ,
>>> output="/var/spool/amavisd/tmp/amavis-20130314T184955-03325-nFS5UJ4F/parts:
>>> lstat() failed: Permission denied. ERROR\n" at (eval 113) line 897.
>>> Mar 14 18:49:55 ip-173-201-189-43 amavis[3325]: (03325-01) (!)WARN: all
>>> primary virus scanners failed, considering backups
>>> *
>>>
>>> *2. Looks destination network not reachable (probably here gmail's mail
>>> server)*
>>> *
>>> Mar 14 18:49:58 ip-173-201-189-43 amavis[3325]: (03325-01) FWD from <
>>> bh...@netcloudjobs.com> -> ,BODY=7BIT 250
>>> 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 1AE0E38A0D3E
>>> Mar 14 18:49:58 ip-173-201-189-43 postfix/error[3384]: 1AE0E38A0D3E: to=<
>>> austin.ein...@gmail.com>, relay=none, delay=0.02, delays=0.01/0.01/0/0,
>>> dsn=4.4.1, status=deferred (delivery temporarily suspended: connect to
>>> alt2.gmail-smtp-in.l.google.com[2607:f8b0:4002:c04::1a]:25: Network is
>>> unreachable)
>>> Mar 14 18:49:58 ip-173-201-189-43 amavis[3325]: (03325-01) Passed CLEAN
>>> {RelayedOutbound}, MYNETS LOCAL [127.0.0.1]:46504 [127.0.0.1] <
>>> bh...@netcloudjobs.com> -> , Message-ID: <
>>> bd17726f3d35c7980426e4a55566c...@netcloudjobs.com>, mail_id:
>>> T8Zt2QE1Eico, Hits: -1, size: 805, queued_as: 1AE0E38A0D3E, 2885 ms
>>> *
>>> Is it a dns issue. Why my mail server is saying "*delivery temporarily
>>> suspended: connect to
>>> alt2.gmail-smtp-in.l.google.com[2607:f8b0:4002:c04::1a]:25:
>>> Network is unreachable)*".
>>>
>>> Kindly guide me to solve these 2 issues.
>>>
>>> Best regards
>>> Austin
>>>
>>>
>>>
>>>
>>>
>>
>
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Postfix/Amavisd/Clamd - Mail send failing
On Thu, Mar 14, 2013 at 10:50 PM, Austin Einter wrote: > I just checked firewall. tcp/smtp(25 ) is allowed. > > Any kind of DNS configuration issues > > Any pointers . > Some ISP's block port 25 if it is a 'home' type connection. Comcast recently started blocking and I can't connect there from home either. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Postfix/Amavisd/Clamd - Mail send failing
On 3/14/2013 9:20 PM, Les Mikesell wrote: > Some ISP's block port 25 if it is a 'home' type connection. Comcast > recently started blocking and I can't connect there from home either. configure your mail server to use your ISP's mail server as a 'smarthost', OR configure it to use an external (coloc or whatever) server as smarthost via port 587 with authentication. -- john r pierce 37N 122W somewhere on the middle of the left coast ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] usb device path/name translating
On 03/13/2013 04:01 PM, zGreenfelder wrote: > does anyone have some pointers for translating these > device numbers/paths to the physical hardware? It looks like Linux is unable to assign an ID to this device. Without that, it won't be able to get any more information about the hardware. IDs are assigned by the host, so there's no generic means of translation. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Postfix/Amavisd/Clamd - Mail send failing
Thanks John By the way I checked with my service provider. Their ISP does not block 25. But to successfully deliver SMTP mail, I need to use their relay server (it uses port 25 only). Where will I configure their relay server . Is it in /etc/postfix/main.cfor any other file. Do I need to modify anyting in dovecot or amavisd configuration??? Thanks Austin On Fri, Mar 15, 2013 at 9:55 AM, John R Pierce wrote: > On 3/14/2013 9:20 PM, Les Mikesell wrote: > > Some ISP's block port 25 if it is a 'home' type connection. Comcast > > recently started blocking and I can't connect there from home either. > > > configure your mail server to use your ISP's mail server as a > 'smarthost', OR configure it to use an external (coloc or whatever) > server as smarthost via port 587 with authentication. > > > > > -- > john r pierce 37N 122W > somewhere on the middle of the left coast > > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Postfix/Amavisd/Clamd - Mail send failing
Thanks Everybody I configured the relayhost entry in main.cf in /etc/postfix path as relayhost = [my service provider relay host] Thats all, I am able to send / recv email. Next how do I make sure, my spam/antivirus filtering is working properly Is it that only maillog i cam check, or is there any effective way of checking it. Thanks -Austin On Fri, Mar 15, 2013 at 11:13 AM, Austin Einter wrote: > Thanks John > By the way I checked with my service provider. Their ISP does not block > 25. But to successfully deliver SMTP mail, I need to use their relay server > (it uses port 25 only). > > Where will I configure their relay server . Is it in /etc/postfix/main.cfor > any other file. Do I need to modify anyting in dovecot or amavisd > configuration??? > > Thanks > Austin > > > > On Fri, Mar 15, 2013 at 9:55 AM, John R Pierce wrote: > >> On 3/14/2013 9:20 PM, Les Mikesell wrote: >> > Some ISP's block port 25 if it is a 'home' type connection. Comcast >> > recently started blocking and I can't connect there from home either. >> >> >> configure your mail server to use your ISP's mail server as a >> 'smarthost', OR configure it to use an external (coloc or whatever) >> server as smarthost via port 587 with authentication. >> >> >> >> >> -- >> john r pierce 37N 122W >> somewhere on the middle of the left coast >> >> ___ >> CentOS mailing list >> CentOS@centos.org >> http://lists.centos.org/mailman/listinfo/centos >> > > ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
