# Segmentation Fault **URL:** \ **Category:** SLES Updates\ **Created:** [October 14, 2016, 10:10pm UTC](https://forums.suse.com/t/segmentation-fault/28789 "2016-10-14T22:10:04Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![silentlenn](https://avatars.discourse-cdn.com/v4/letter/s/f1d935/32.png) [@silentlenn](https://forums.suse.com/u/silentlenn)\ **Post date:** [October 14, 2016, 10:10pm UTC](https://forums.suse.com/t/segmentation-fault/28789/1 "2016-10-14T22:10:04Z")
Within the past week I am all of a sudden getting “Segmentation Fault” when I run zypper up. If I disable all repositories, no problem. I have tried various things: zypper refresh-services -r OR zypper ref -s Refreshing service ‘nu\_novell\_com’. Segmentation fault zypper ref Segmenation fault Thoughts? ---
**Author:** ![ab1](https://avatars.discourse-cdn.com/v4/letter/a/d2c977/32.png) [@ab1](https://forums.suse.com/u/ab1)\ **Post date:** [October 14, 2016, 11:06pm UTC](https://forums.suse.com/t/segmentation-fault/28789/2 "2016-10-14T23:06:31Z")
Since that should NEVER happen, I’d probably try to find the repo that causes the problem and then go from there Is it always the nu\_novell\_com one that causes the fault? What if you add a normal ISO or something and refresh from there? Any updates recently that may be linked to this? Which SLES version/SP are you running? Any other similar boxes, and if so do they have the same issue? – Good luck. If you find this post helpful and are logged into the web interface, show your appreciation and click on the star below… ---
**Author:** ![silentlenn](https://avatars.discourse-cdn.com/v4/letter/s/f1d935/32.png) [@silentlenn](https://forums.suse.com/u/silentlenn)\ **Post date:** [October 17, 2016, 4:49pm UTC](https://forums.suse.com/t/segmentation-fault/28789/3 "2016-10-17T16:49:21Z")
I am running SLES 11 SP4. I do have another box running SLES 11 SP4 which is able to update without issue. Other than standard updates the only thing I am doing with this box is prepping it to be my primary GroupWise server so I have made some mounted connections to run the migration tool. It definitely is an issue with the repositories but I am going to admit that I am definitely new to this level of Linux system management so though I know what you mean, I am not necessarily up to speed on how to accomplish what you are suggesting and with what. If I disable all repositories ZYPPER UP runs fine and of course returns “Nothing to Do” What alternate repository should I use besides nu\_novell? I have seen where you can go in and add repositories, but I am not confident that I am setting them up properly. ---
**Author:** ![Jens-U](https://avatars.discourse-cdn.com/v4/letter/j/d78d45/32.png) [@Jens-U](https://forums.suse.com/u/Jens-U)\ **Post date:** [October 17, 2016, 5:07pm UTC](https://forums.suse.com/t/segmentation-fault/28789/4 "2016-10-17T17:07:54Z")
Hi, suggestion #1: run “ldconfig” once, before further testing zypper commands. [QUOTE=silentlenn;34753][…] If I disable all repositories ZYPPER UP runs fine and of course returns “Nothing to Do” What alternate repository should I use besides nu\_novell? I have seen where you can go in and add repositories, but I am not confident that I am setting them up properly.[/QUOTE] suggestion #2, from ab: Don’t disable _all_ repositories, but one-by-one to see if it’s a specific repos that causes the problem. Or re-enable one-by-one after disabling all. As ab already said - this shouldn’t happen at all, especially not caused by repos configuration/content. The one instance I’ve had such dubious symptoms was after a partial system update that caused an inconsistently cached library setup - which the applications themselves could do nothing about. Hence my suggestion to run “ldconfig”, which regenerates that cache and links etc. Regards, J ---
**Author:** ![silentlenn](https://avatars.discourse-cdn.com/v4/letter/s/f1d935/32.png) [@silentlenn](https://forums.suse.com/u/silentlenn)\ **Post date:** [October 17, 2016, 5:43pm UTC](https://forums.suse.com/t/segmentation-fault/28789/5 "2016-10-17T17:43:33Z")
Thanks. Yes, I had tried each of the 4 (that match my other functioning machine) repositories on their own. Eventually I took it down to none and tested. Per your suggestion I took the following steps: - enabled 1 repository - ran LDCONFIG (I used lower case, but capped it here for clarity) - ran zypper up - segmentation fault - repeated all steps for the next working repository per my other SLES SP4 machine ---
**Author:** ![Jens-U](https://avatars.discourse-cdn.com/v4/letter/j/d78d45/32.png) [@Jens-U](https://forums.suse.com/u/Jens-U)\ **Post date:** [October 18, 2016, 5:42pm UTC](https://forums.suse.com/t/segmentation-fault/28789/6 "2016-10-18T17:42:48Z")
Too bad this didn’t work out. Depending on how much of your own time you want to spend on hunting this down, you can either verify the installed packages (rpm -Vall) or possibly open a service request. Regards, J