Did an upgrade of my AMD64 from 9.2 to 9.3 and am running into issues.. 1) newt-32bit won't install, I get the following error message ERROR(InstTarget:E_RpmDB_subprocess_failed) --- 2005-04-16 18:37:48 newt-32bit-9.3-7.x86_64.rpm install failed rpm output: error: unpacking of archive failed on file /usr/lib/python: cpio: rename failed - Is a directory 2) nvu won't install, I get the following conflicts.. #### YaST2 conflicts list - generated 2005-04-16 18:37:29 #### nvu 0.80-7 conflict Conflict Resolution: ( ) Ignore Conflict and Risk System Inconsistencies ( ) Do Not Install nvu Unresolved Requirements: nvu requires libxlibrgb.so()(64bit) nvu requires libgtkxtbin.so()(64bit) nvu requires libgtkembedmoz.so()(64bit) nvu requires libgkgfx.so()(64bit) libxlibrgb.so()(64bit) not available Conflict Resolution: ( ) Ignore Conflict and Risk System Inconsistencies ( ) Remove the Referring Package Do Not Install nvu Required by: nvu requires libxlibrgb.so()(64bit) libgtkxtbin.so()(64bit) not available Conflict Resolution: ( ) Ignore Conflict and Risk System Inconsistencies ( ) Remove the Referring Package Do Not Install nvu Required by: nvu requires libgtkxtbin.so()(64bit) libgtkembedmoz.so()(64bit) not available Conflict Resolution: ( ) Ignore Conflict and Risk System Inconsistencies ( ) Remove the Referring Package Do Not Install nvu Required by: nvu requires libgtkembedmoz.so()(64bit) libgkgfx.so()(64bit) not available Conflict Resolution: ( ) Ignore Conflict and Risk System Inconsistencies ( ) Remove the Referring Package Do Not Install nvu Required by: nvu requires libgkgfx.so()(64bit) #### YaST2 conflicts list END ### 3. My mail system is hosed, postfix dies with cryptic messages about inet_interface being configured wrong, for some reason it does not like inet_interfaces = 127.0.0.1 ::1 I got it working by deleting the '::1' but have no clue why I should have to do that. amavisd is screwed up too, it now fails with messages about the primary virus scanner failing Apr 16 18:35:22 helphand amavis[28656]: (28656-03) WARN: all primary virus scanners failed, considering backups that would be clamav, which seems to be running fine, but amavis doesn't agree with me <g>. 4. I'm getting some strange messages in /var/log/warn Apr 16 18:37:47 helphand kernel: UDF-fs: No VRS found Apr 16 18:37:47 helphand hal.hotplug[28870]: DEVPATH is not set Apr 16 18:37:47 helphand hal.hotplug[28873]: DEVPATH is not set No idea what they are telling me. I just *knew* I should have waited before jumping in to 9.3, tracking all this stuff down and trying to fix it is a royal pita. Scott -- POPFile, the OpenSource EMail Classifier http://popfile.sourceforge.net/ Linux 2.6.11.4-20a-default x86_64
On Sunday 17 April 2005 03:48, Scott Leighton wrote:
2) nvu won't install, I get the following conflicts..
#### YaST2 conflicts list - generated 2005-04-16 18:37:29 ####
nvu 0.80-7 conflict
All the files it complains about are provided by mozilla 64bit, so make sure that is selected for installation. Not sure why yast can't find it
3. My mail system is hosed, postfix dies with cryptic messages about inet_interface being configured wrong, for some reason it does not like
inet_interfaces = 127.0.0.1 ::1
I got it working by deleting the '::1' but have no clue why I should have to do that.
My postfix works with that line. Did you disable ipv6 at some point?
4. I'm getting some strange messages in /var/log/warn
Apr 16 18:37:47 helphand kernel: UDF-fs: No VRS found
This just means that you've inserted a CD, not a DVD or CDRW. The system tries to autodetect the file system, and UDF is tried before ISO9660. It's not important.
Apr 16 18:37:47 helphand hal.hotplug[28870]: DEVPATH is not set Apr 16 18:37:47 helphand hal.hotplug[28873]: DEVPATH is not set
No idea what they are telling me.
Only that some hotplug event that doesn't involve a device has happened. Mostly it seems to be that you've inserted an optical disk. Again, nothing to worry about
Anders Johansson wrote:
On Sunday 17 April 2005 03:48, Scott Leighton wrote:
2) nvu won't install, I get the following conflicts..
#### YaST2 conflicts list - generated 2005-04-16 18:37:29 ####
nvu 0.80-7 conflict
All the files it complains about are provided by mozilla 64bit, so make sure that is selected for installation. Not sure why yast can't find it
OK, I'll explore that one as a possibility. I know it installed a mozilla, not sure which one it installed though. nvu is the least of my problems at the moment <g>.
3. My mail system is hosed, postfix dies with cryptic messages about inet_interface being configured wrong, for some reason it does not like
inet_interfaces = 127.0.0.1 ::1
I got it working by deleting the '::1' but have no clue why I should have to do that.
My postfix works with that line. Did you disable ipv6 at some point?
If I did, I'm not aware of doing it. I suppose I could have at some point long ago disabled it, but I haven't touched my mail config in ages and 9.2 and 9.1 never complained about the inet_interface. I'm about ready to uninstall all of the mail related stuff and try a clean reinstall, something is hosed badly. I am replying to this from gmail, I can't get mail on the suse box, kmail doesn't seem to recognize that mail exists in /var/mail/helphand mutt complains that /var/mail/helphand is not a mailbox, the only way I saw your message is that procmail is working and forwarded it to my gmail account. I can see the mbox file /var/mail/helphand and it is full of mail, so I am once again clueless as to what the friggin problem is. Man, I'm flustrated, and I haven't even started on the stuff I expected to have problems with, like Xine and Mplayer. Scott
Scott Leighton wrote:
Anders Johansson wrote:
On Sunday 17 April 2005 03:48, Scott Leighton wrote:
2) nvu won't install, I get the following conflicts..
#### YaST2 conflicts list - generated 2005-04-16 18:37:29 ####
nvu 0.80-7 conflict
All the files it complains about are provided by mozilla 64bit, so make sure that is selected for installation. Not sure why yast can't find it
OK, I'll explore that one as a possibility. I know it installed a mozilla, not sure which one it installed though. nvu is the least of my problems at the moment <g>.
That was it, apparently it installed the i586 version. I toggled it to the x86_64 rpm and changed the checkmark to an update, installed it, went back and tried to then install nvu and it installed just fine with no issues. Good catch, I never would have figured that one out on my own. Scott
On Saturday 16 April 2005 7:45 pm, Scott Leighton wrote:
Anders Johansson wrote:
On Sunday 17 April 2005 03:48, Scott Leighton wrote:
2) nvu won't install, I get the following conflicts..
#### YaST2 conflicts list - generated 2005-04-16 18:37:29 ####
nvu 0.80-7 conflict
All the files it complains about are provided by mozilla 64bit, so make sure that is selected for installation. Not sure why yast can't find it
OK, I'll explore that one as a possibility. I know it installed a mozilla, not sure which one it installed though. nvu is the least of my problems at the moment <g>.
3. My mail system is hosed, postfix dies with cryptic messages about inet_interface being configured wrong, for some reason it does not like
inet_interfaces = 127.0.0.1 ::1
I got it working by deleting the '::1' but have no clue why I should have to do that.
My postfix works with that line. Did you disable ipv6 at some point?
If I did, I'm not aware of doing it. I suppose I could have at some point long ago disabled it, but I haven't touched my mail config in ages and 9.2 and 9.1 never complained about the inet_interface.
I'm about ready to uninstall all of the mail related stuff and try a clean reinstall, something is hosed badly. I am replying to this from gmail, I can't get mail on the suse box, kmail doesn't seem to recognize that mail exists in /var/mail/helphand mutt complains that /var/mail/helphand is not a mailbox, the only way I saw your message is that procmail is working and forwarded it to my gmail account.
I can see the mbox file /var/mail/helphand and it is full of mail, so I am once again clueless as to what the friggin problem is. Man, I'm flustrated, and I haven't even started on the stuff I expected to have problems with, like Xine and Mplayer.
It pains me to say this, but the 'windows solution' worked to solve my incoming mail problem. I rebooted. After the reboot, Kmail and Mutt both had no problem with /var/mail/helphand. Go figure. Scott -- POPFile, the OpenSource EMail Classifier http://popfile.sourceforge.net/ Linux 2.6.11.4-20a-default x86_64
On Saturday 16 April 2005 7:45 pm, Scott Leighton wrote:
Man, I'm flustrated, and I haven't even started on the stuff I expected to have problems with, like Xine and Mplayer.
Well, looks like the reboot solved the remaining issues. And, counter to my expectations, Xine and Mplayer were a breeze, a quick trip to packman's site got all the x86_64 rpm's I needed and installing was a breeze. Much much easier than the hassles I experienced with both 9.1 and 9.2. Scott -- POPFile, the OpenSource EMail Classifier http://popfile.sourceforge.net/ Linux 2.6.11.4-20a-default x86_64
The Saturday 2005-04-16 at 19:45 -0700, Scott Leighton wrote:
3. My mail system is hosed, postfix dies with cryptic messages about inet_interface being configured wrong, for some reason it does not like
inet_interfaces = 127.0.0.1 ::1
I got it working by deleting the '::1' but have no clue why I should have to do that.
My postfix works with that line. Did you disable ipv6 at some point?
If I did, I'm not aware of doing it. I suppose I could have at some point long ago disabled it, but I haven't touched my mail config in ages and 9.2 and 9.1 never complained about the inet_interface.
It seems that the new postfix is stricter about somethings. I had a
similar error.
I had:
#mynetworks = 192.168.100.2/8 127.0.0.0/8
the correct thing is:
mynetworks = 192.0.0.0/8, 127.0.0.0/8
and the error was really cryptic:
Apr 23 13:02:49 nimrodel amavis[12863]: (12863-01) mail_via_smtp: 450
4.4.1 Can't connect to 127.0.0.1 port 10025, Bad file descriptor at
/usr/sbin/amavisd line 3805, <GEN4> line 29., id=12863-01
Apr 23 13:02:49 nimrodel postfix/master[12947]: warning: process
/usr/lib/postfix/smtpd pid 12978 exit status 1
Apr 23 13:02:49 nimrodel amavis[12863]: (12863-01) Blocked CLEAN,
On Monday, April 25, 2005 08:30 pm, Carlos E. R. wrote:
It seems that the new postfix is stricter about somethings. I had a similar error.
I had:
#mynetworks = 192.168.100.2/8 127.0.0.0/8
the correct thing is:
mynetworks = 192.0.0.0/8, 127.0.0.0/8
Carlos, I think perhaps you may want: mynetworks = 192.168.100.0/24 127.0.0.0/8 The comma is optional; Postfix doesn't care. 192.168.100.2/8 is not correct CIDR notation syntax. /24 is equivalent to a netmask of 255.255.255.0. If you leave 192.168.0.0/8, then any host with an IP of 192.168.xxx.yyy Postfix will think is on your local network. I'm assuming you have only one Class C subnet, with all addresses 192.168.100.xxx, yes? Best regards, Mark -- _________________________________________________________ A Message From... L. Mark Stone Reliable Networks of Maine, LLC "We manage your network so you can manage your business." 477 Congress Street Portland, ME 04101 Tel: (207) 772-5678 Web: http://www.rnome.com
The Monday 2005-04-25 at 23:32 -0400, L. Mark Stone wrote:
Carlos, I think perhaps you may want:
mynetworks = 192.168.100.0/24 127.0.0.0/8
The comma is optional; Postfix doesn't care. 192.168.100.2/8 is not correct CIDR notation syntax. /24 is equivalent to a netmask of 255.255.255.0.
If you leave 192.168.0.0/8, then any host with an IP of 192.168.xxx.yyy Postfix will think is on your local network. I'm assuming you have only one Class C subnet, with all addresses 192.168.100.xxx, yes?
Yes, you are right. It doesn't matter much, just my home, internal, network of two PCs X-) I have corrected it per your sugerence, thanks :-) -- Cheers, Carlos Robinson
Scott Leighton wrote:
Did an upgrade of my AMD64 from 9.2 to 9.3 and am running into issues..
1) newt-32bit won't install, I get the following error message
ERROR(InstTarget:E_RpmDB_subprocess_failed) --- 2005-04-16 18:37:48 newt-32bit-9.3-7.x86_64.rpm install failed rpm output: error: unpacking of archive failed on file /usr/lib/python: cpio: rename failed - Is a directory
Don't know what caused it, but I solved this one by deleting the directory /usr/lib/python and deleting a bunch of symlinks in the form of python:3ALKD4 in /usr/lib that were all dated today and appear to have been temporary links created by the retries I did trying to install newt-32bit. Once I deleted that stuff, Yast went ahead and successfully installed newt-32bit. Have no idea why or how the empty /usr/lib/python directory got on my system, but looks like the newt-32bit install didn't like it one bit. Scott
participants (4)
-
Anders Johansson -
Carlos E. R. -
L. Mark Stone -
Scott Leighton