Re: portupgrade system destruction?
On Tue, Jan 04, 2005 at 04:04:02PM +, Andrew Sinclair wrote: Portupgrade makes a mess at the best of times. A recursive portupgrade is not so clever about dependencies, particually on a live system. On occasion, it even seems to tamper with core libraries which is what would have occured in your case. Can you provide some evidence of these claims? I'm suspicious :-) Kris pgp1QVBAUDGAF.pgp Description: PGP signature
Re: portupgrade system destruction?
Kris Kennaway wrote: On Tue, Jan 04, 2005 at 04:04:02PM +, Andrew Sinclair wrote: Portupgrade makes a mess at the best of times. A recursive portupgrade is not so clever about dependencies, particually on a live system. On occasion, it even seems to tamper with core libraries which is what would have occured in your case. Can you provide some evidence of these claims? I'm suspicious :-) Kris No, I can only tell you that I tried it, and stopped using it some time ago because of similar problems. Keep in mind I said, seems to tamper with. I had an issue where some kind of linux centric library (not libc-client) was no longer available and several system utilities refused to start up. I tried reinstalling linux_base but that didn't fix it. Turned out it was a subtle change in the ports collection that required a little more than a [cvsup; portupgrade] to fix. On previous occasions, it attempted to upgrade 10x as many ports dependencies as I wanted. It was more work than a manual deinstall, cvsup, reinstall. I came to the conclusion that automated tools are a poor excuse for not reading /usr/ports/UPDATING ;-) I usually research these problems before I say anything but figuring that Mr Anderson required immediate assistance, I risked using the infamous Ass-U-Me technique to speculate about the problem. Had I have known you'd be on his case the same day, I would not have said anything. By the way, sorry if I offended you with the, with all due respect, quip Eric. I wasn't sure how to write that in a way that didn't seem offensive. :-) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade system destruction?
Moved to freebsd-questions by Andrew Sinclair. Eric Anderson wrote: I have a few dedicated servers at a hosting company (about 3 hours drive time away). On one of the systems I ran a 'portupgrade -arR' this morning, and then disconnected (I ran it in a screen session). About an hour later, I realized I could not log in anymore via ssh. Seems that I can connect, but my passwords fail (permission denied). I can't FTP in, or check mail with any username/password combos. Even my preshared SSH keys do not work. When connecting via POP, I get this message: Connected to hostname. Escape character is '^]'. /usr/libexec/ld-elf.so.1: Shared object libc-client4.so.8 not found Connection closed by foreign host. Can anyone help me figure out what may have gone wrong? And even how I might be able to fix it remotely, or walk someone through a fix? Portupgrade makes a mess at the best of times. A recursive portupgrade is not so clever about dependencies, particually on a live system. On occasion, it even seems to tamper with core libraries which is what would have occured in your case. With all due respect, you better have a disaster recovery plan. You said one of the systems. That's a good sign. Core library dependancies like libc are a bitch to deal with. My approach would be to reinstall a release on the existing system image, then restore the overwritten /etc files from a recent backup or an identical server. First, install the same release version on your PC. Build a custom kernel for the server (it's better to monitor the build locally). Tarball the files to be installed, send it to work and get one of the admins to do the following: 1. Burn your chosen release CD 2. Insert into affected servers slot-load and reboot, reinstalling everything (including sources) 2. Extract the kernel and LKM's tarball you uploaded to / 3. Restore /etc from backup. 4. Reboot and watch for errors on the console This should get you running again but you might have to fix some ports manually. The reason I didn't suggest restoring your complete OS from backup is because an older version may not like your ports. I think it saves time but it's your call. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
