Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #203870 > unrolled thread

Upgrade Problem

Back to article view | Back to linux.debian.user

Contents

  Upgrade Problem "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2019-01-03 16:00 +0100
    Fwd: Upgrade Problem "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2019-01-03 17:20 +0100
      Re: Fwd: Upgrade Problem steve <dlist@bluewin.ch> - 2019-01-03 17:40 +0100
        Re: Upgrade Problem Brad Rogers <brad@fineby.me.uk> - 2019-01-03 18:30 +0100
          Re: Upgrade Problem "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2019-01-03 18:40 +0100
      Re: Fwd: Upgrade Problem deloptes <deloptes@gmail.com> - 2019-01-03 17:40 +0100
        Re: Fwd: Upgrade Problem "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2019-01-03 18:20 +0100
        Re: Fwd: Upgrade Problem deloptes <deloptes@gmail.com> - 2019-01-03 18:40 +0100
          Re: Fwd: Upgrade Problem Greg Wooledge <wooledg@eeg.ccf.org> - 2019-01-03 19:00 +0100
            Re: Fwd: Upgrade Problem "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2019-01-03 20:40 +0100
              Re: Fwd: Upgrade Problem Greg Wooledge <wooledg@eeg.ccf.org> - 2019-01-03 20:50 +0100
              Re: Fwd: Upgrade Problem Greg Wooledge <wooledg@eeg.ccf.org> - 2019-01-03 20:50 +0100
                Re: Fwd: Upgrade Problem "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2019-01-03 21:20 +0100
                  Re: Fwd: Upgrade Problem deloptes <deloptes@gmail.com> - 2019-01-03 21:30 +0100
                    Re: Fwd: Upgrade Problem Nicolas George <george@nsup.org> - 2019-01-03 21:40 +0100
                      Re: Fwd: Upgrade Problem deloptes <deloptes@gmail.com> - 2019-01-03 22:20 +0100
                  Re: Fwd: Upgrade Problem Frank Weißer <linux@weisser-ol.de> - 2019-01-04 10:30 +0100
              Re: Fwd: Upgrade Problem "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2019-01-03 21:40 +0100
                Re: Fwd: Upgrade Problem Nicolas George <george@nsup.org> - 2019-01-03 22:30 +0100
                  Re: Fwd: Upgrade Problem Roberto C. Sánchez <roberto@debian.org> - 2019-01-03 23:00 +0100
                    Re: Fwd: Upgrade Problem Nicolas George <george@nsup.org> - 2019-01-03 23:30 +0100
                      Re: Fwd: Upgrade Problem deloptes <deloptes@gmail.com> - 2019-01-04 01:30 +0100
                        Re: Fwd: Upgrade Problem Nicolas George <george@nsup.org> - 2019-01-04 11:20 +0100
                          Re: Fwd: Upgrade Problem Roberto C. Sánchez <roberto@debian.org> - 2019-01-04 13:40 +0100
                            Re: Fwd: Upgrade Problem Nicolas George <george@nsup.org> - 2019-01-04 13:40 +0100
                              Re: Fwd: Upgrade Problem deloptes <deloptes@gmail.com> - 2019-01-04 19:00 +0100
                                Re: Fwd: Upgrade Problem Nicolas George <george@nsup.org> - 2019-01-04 19:40 +0100
                                  Re: Fwd: Upgrade Problem Gene Heskett <gheskett@shentel.net> - 2019-01-04 20:00 +0100
                                    Re: Fwd: Upgrade Problem Roberto C. Sánchez <roberto@debian.org> - 2019-01-04 20:40 +0100
                                      Re: Fwd: Upgrade Problem Roberto C. Sánchez <roberto@debian.org> - 2019-01-04 21:20 +0100
                                      Re: Fwd: Upgrade Problem Brian <ad44@cityscape.co.uk> - 2019-01-04 21:20 +0100
                                    Re: Fwd: Upgrade Problem Brian <ad44@cityscape.co.uk> - 2019-01-04 20:40 +0100
                                      Re: Fwd: Upgrade Problem Gene Heskett <gheskett@shentel.net> - 2019-01-04 22:10 +0100
                                        Re: Fwd: Upgrade Problem mick crane <mick.crane@gmail.com> - 2019-01-05 08:20 +0100
                                    Re: Fwd: Upgrade Problem deloptes <deloptes@gmail.com> - 2019-01-04 20:50 +0100
                                  Re: Fwd: Upgrade Problem Brian <ad44@cityscape.co.uk> - 2019-01-04 20:40 +0100
                                    Re: Fwd: Upgrade Problem deloptes <deloptes@gmail.com> - 2019-01-04 20:50 +0100
                  Re: Fwd: Upgrade Problem Andy Smith <andy@strugglers.net> - 2019-01-03 23:10 +0100
                    Re: Fwd: Upgrade Problem Curt <curty@free.fr> - 2019-01-04 14:10 +0100
                Re: Fwd: Upgrade Problem Gene Heskett <gheskett@shentel.net> - 2019-01-04 03:30 +0100
                  Re: Fwd: Upgrade Problem Greg Wooledge <wooledg@eeg.ccf.org> - 2019-01-04 14:20 +0100
                    Re: Fwd: Upgrade Problem Gene Heskett <gheskett@shentel.net> - 2019-01-04 14:50 +0100
                      Re: Fwd: Upgrade Problem Greg Wooledge <wooledg@eeg.ccf.org> - 2019-01-04 15:00 +0100
                        Re: Fwd: Upgrade Problem deloptes <deloptes@gmail.com> - 2019-01-04 19:30 +0100
                          Re: Fwd: Upgrade Problem Nicolas George <george@nsup.org> - 2019-01-04 19:40 +0100
                            Re: Fwd: Upgrade Problem deloptes <deloptes@gmail.com> - 2019-01-04 21:00 +0100
                              Re: Upgrade Problem Joe <joe@jretrading.com> - 2019-01-04 21:30 +0100
                                Re: Upgrade Problem deloptes <deloptes@gmail.com> - 2019-01-04 23:00 +0100
                          Re: Fwd: Upgrade Problem Gene Heskett <gheskett@shentel.net> - 2019-01-04 19:50 +0100
                            Re: Fwd: Upgrade Problem deloptes <deloptes@gmail.com> - 2019-01-05 01:40 +0100
                              Re: Fwd: Upgrade Problem Gene Heskett <gheskett@shentel.net> - 2019-01-05 06:30 +0100
                      Re: Fwd: Upgrade Problem <tomas@tuxteam.de> - 2019-01-04 15:50 +0100
                    Re: Fwd: Upgrade Problem David Wright <deblis@lionunicorn.co.uk> - 2019-01-04 18:10 +0100
              Re: Fwd: Upgrade Problem Nicolas George <george@nsup.org> - 2019-01-03 21:40 +0100
          Re: Fwd: Upgrade Problem Nicolas George <george@nsup.org> - 2019-01-03 19:00 +0100
          Re: Fwd: Upgrade Problem "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2019-01-03 19:00 +0100
            Re: Fwd: Upgrade Problem deloptes <deloptes@gmail.com> - 2019-01-03 20:20 +0100
              Re: Fwd: Upgrade Problem "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2019-01-03 20:50 +0100
                Re: Fwd: Upgrade Problem deloptes <deloptes@gmail.com> - 2019-01-03 21:40 +0100
                  Re: Fwd: Upgrade Problem "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2019-01-03 21:50 +0100
                    Re: Fwd: Upgrade Problem deloptes <deloptes@gmail.com> - 2019-01-03 22:10 +0100
                      Re: Fwd: Upgrade Problem songbird <songbird@anthive.com> - 2019-01-04 03:20 +0100
                        Re: Fwd: Upgrade Problem deloptes <deloptes@gmail.com> - 2019-01-04 09:10 +0100
                    Re: Fwd: Upgrade Problem Gene Heskett <gheskett@shentel.net> - 2019-01-04 03:40 +0100
                    Re: Upgrade Problem Felix Miata <mrmazda@earthlink.net> - 2019-01-04 04:50 +0100
                      Re: Upgrade Problem Andy Smith <andy@strugglers.net> - 2019-01-04 09:50 +0100
                        Overhead of LVM (Re: Upgrade Problem) rhkramer@gmail.com - 2019-01-04 14:20 +0100
                          Re: Overhead of LVM (Re: Upgrade Problem) Reco <recoverym4n@enotuniq.net> - 2019-01-04 14:30 +0100
                            Re: Overhead of LVM (Re: Upgrade Problem) rhkramer@gmail.com - 2019-01-05 05:10 +0100
                              Re: Overhead of LVM (Re: Upgrade Problem) Reco <recoverym4n@enotuniq.net> - 2019-01-05 08:40 +0100
                        Re: Upgrade Problem Richard Hector <richard@walnut.gen.nz> - 2019-01-04 21:10 +0100
                          Re: Upgrade Problem Stefan Krusche <linux@stefan-krusche.de> - 2019-03-10 14:30 +0100
                      Re: Upgrade Problem Nicolas George <george@nsup.org> - 2019-01-04 11:20 +0100
    Re: Upgrade Problem Patrick Bartek <nemommxiv@gmail.com> - 2019-01-03 18:20 +0100
      Re: Upgrade Problem "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2019-01-03 18:40 +0100
        Re: Upgrade Problem Patrick Bartek <nemommxiv@gmail.com> - 2019-01-04 03:20 +0100
          Re: Upgrade Problem Matthew Crews <mailinglists@mattcrews.com> - 2019-01-04 03:50 +0100
            Re: Upgrade Problem Andy Smith <andy@strugglers.net> - 2019-01-04 10:00 +0100
              Re: Upgrade Problem Felix Miata <mrmazda@earthlink.net> - 2019-01-04 10:40 +0100
                Re: Upgrade Problem David Wright <deblis@lionunicorn.co.uk> - 2019-01-04 17:30 +0100
                  Re: Upgrade Problem Felix Miata <mrmazda@earthlink.net> - 2019-01-04 19:50 +0100
                    Re: Upgrade Problem David Wright <deblis@lionunicorn.co.uk> - 2019-01-04 21:30 +0100
                      Re: allocating disk space (was: Upgrade Problem) Felix Miata <mrmazda@earthlink.net> - 2019-01-05 01:40 +0100
                        Re: allocating disk space (was: Upgrade Problem) David Wright <deblis@lionunicorn.co.uk> - 2019-01-10 01:10 +0100
                          Re: allocating disk space Felix Miata <mrmazda@earthlink.net> - 2019-01-11 08:20 +0100
                            Re: allocating disk space David Wright <deblis@lionunicorn.co.uk> - 2019-01-13 14:20 +0100
              Re: Upgrade Problem Brian <ad44@cityscape.co.uk> - 2019-01-04 11:50 +0100
                Re: Upgrade Problem Reco <recoverym4n@enotuniq.net> - 2019-01-04 13:00 +0100
                Re: Upgrade Problem Greg Wooledge <wooledg@eeg.ccf.org> - 2019-01-04 14:30 +0100
    Re: Upgrade Problem songbird <songbird@anthive.com> - 2019-01-03 20:00 +0100
      Re: Upgrade Problem "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2019-01-03 20:40 +0100
        Re: Upgrade Problem David Wright <deblis@lionunicorn.co.uk> - 2019-01-03 21:00 +0100
          Re: Upgrade Problem Greg Wooledge <wooledg@eeg.ccf.org> - 2019-01-03 21:10 +0100
        Re: Upgrade Problem Michael Stone <mstone@debian.org> - 2019-01-04 16:00 +0100

Page 1 of 5  [1] 2 3 4 5  Next page →

#203870 — Upgrade Problem

I am running Debian Stretch  and have just encountered a problem during 
a routine apt-get dist-upgrade.

Specifically, it failed with the following error messages.

E: libc-bin: subprocess installed post-installation script returned 
error exit status 1

Please advise.

Thanks in advance.

-- 
Stephen P. Molnar, Ph.D.
Consultant
www.molecular-modeling.net
(614)312-7528 (c)
Skype: smolnar1

[toc] | [next] | [standalone]

#203873

[Multipart message — attachments visible in raw view] — view raw

This is an addendum to my original message.

Einstein defined insanity as: "trying the same thing and expecting a 
different answer". In spite of that I tried apt-get dist-upgrade again 
and got:

root@AbNormal:/home/comp# apt dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
   libarchive13 tzdata
2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 0 B/567 kB of archives.
After this operation, 12.3 kB of additional disk space will be used.
Do you want to continue? [Y/n]

Accepting the default I got:

ldconfig: Writing of cache data failed: No such file or directory
dpkg: error processing package libc-bin (--configure):
  subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
  libc-bin
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@AbNormal:/home/comp#

slightly different from my first message.

-------- Forwarded Message --------
Subject: 	Upgrade Problem
Date: 	Thu, 3 Jan 2019 09:54:44 -0500
From: 	Stephen P. Molnar <s.molnar@sbcglobal.net>
To: 	debian-user@lists.debian.org



I am running Debian Stretch  and have just encountered a problem during
a routine apt-get dist-upgrade.

Specifically, it failed with the following error messages.

E: libc-bin: subprocess installed post-installation script returned
error exit status 1

Please advise.

Thanks in advance.

-- 
Stephen P. Molnar, Ph.D.
Consultant
www.molecular-modeling.net
(614)312-7528 (c)
Skype: smolnar1

[toc] | [prev] | [next] | [standalone]

#203877

Hi Stephan,

Perhaps have you become root with 'su' only. A couple of weeks ago, I
had the same problem. It seems su behaviour has changed recently. I
tried 'su -' to become root, and the error disappeared. 

I guess some reading of su changelog file might explain this. But too lazy
for that.

Hope it helps.

Best,
Steve

[toc] | [prev] | [next] | [standalone]

#203881

[Multipart message — attachments visible in raw view] — view raw

On Thu, 3 Jan 2019 17:33:20 +0100
steve <dlist@bluewin.ch> wrote:

Hello steve,

>had the same problem. It seems su behaviour has changed recently. I

It changed several months ago.  I got notification 8 Aug 2018.

As you go on to point out, 'su -' should permit OP to update without
problem.

-- 
 Regards  _
         / )           "The blindingly obvious is
        / _)rad        never immediately apparent"
Why do they try to hide our past pulling down houses and build car parks
Bricks & Mortar - The Jam

[toc] | [prev] | [next] | [standalone]

#203883

On 01/03/2019 11:43 AM, Brad Rogers wrote:
> On Thu, 3 Jan 2019 17:33:20 +0100
> steve <dlist@bluewin.ch> wrote:
>
> Hello steve,
>
>> had the same problem. It seems su behaviour has changed recently. I
> It changed several months ago.  I got notification 8 Aug 2018.
>
> As you go on to point out, 'su -' should permit OP to update without
> problem.
>
su - didn't work.  GOt the same error messages.

-- 
Stephen P. Molnar, Ph.D.
Consultant
www.molecular-modeling.net
(614)312-7528 (c)
Skype: smolnar1

[toc] | [prev] | [next] | [standalone]

#203878

Stephen P. Molnar wrote:

> ldconfig: Writing of cache data failed: No such file or directory
> dpkg: error processing package libc-bin (--configure):
> subprocess installed post-installation script returned error exit status 1

man ldconfig -> cache default is /etc/ld.so.cache

Was it altered and you forgot? Or is it someting wrong with the default
cache file

$ ls -al /etc/ld.so.cache
-rw-r--r-- 1 root root 176004 Jan  1 21:56 /etc/ld.so.cache

regards

[toc] | [prev] | [next] | [standalone]

#203880

On 01/03/2019 11:29 AM, deloptes wrote:
> Stephen P. Molnar wrote:
>
>> ldconfig: Writing of cache data failed: No such file or directory
>> dpkg: error processing package libc-bin (--configure):
>> subprocess installed post-installation script returned error exit status 1
> man ldconfig -> cache default is /etc/ld.so.cache
>
> Was it altered and you forgot? Or is it someting wrong with the default
> cache file
>
> $ ls -al /etc/ld.so.cache
> -rw-r--r-- 1 root root 176004 Jan  1 21:56 /etc/ld.so.cache
>
> regards
>
Thanks for your reply.

I haven't, at least knowingly, altered the file.  I don't really mess 
around the the OS, other than to keep it updated via apt or apt-get.

Can it be restored?

-- 
Stephen P. Molnar, Ph.D.
Consultant
www.molecular-modeling.net
(614)312-7528 (c)
Skype: smolnar1

[toc] | [prev] | [next] | [standalone]

#203884

deloptes wrote:

> man ldconfig -> cache default is /etc/ld.so.cache
> 
> Was it altered and you forgot? Or is it someting wrong with the default
> cache file
> 
> $ ls -al /etc/ld.so.cache
> -rw-r--r-- 1 root root 176004 Jan  1 21:56 /etc/ld.so.cache

as root try 

touch /etc/ld.so.cache

run manually ldconfig and perform the upgrade again 

check if you have also the rest of ldconfig - at least /etc/ld.so.conf

best would be if you had backup and knew what was there before

regards

[toc] | [prev] | [next] | [standalone]

#203885

On Thu, Jan 03, 2019 at 12:49:48PM -0500, Stephen P. Molnar wrote:
> root@AbNormal:/home/comp# ldconfig
> ldconfig: Writing of cache data failed: No such file or directory

You NEED to figure out why this is happening.  Is the entire /etc
directory gone, or something?

Show some basic initiative.  Look around.  Show us what abnormal things
are going on with your system.

ls -ld / /etc /etc/ld.*
strace /sbin/ldconfig

Do something, do ANYTHING useful!

[toc] | [prev] | [next] | [standalone]

#203894

On 01/03/2019 12:53 PM, Greg Wooledge wrote:
> On Thu, Jan 03, 2019 at 12:49:48PM -0500, Stephen P. Molnar wrote:
>> root@AbNormal:/home/comp# ldconfig
>> ldconfig: Writing of cache data failed: No such file or directory
> You NEED to figure out why this is happening.  Is the entire /etc
> directory gone, or something?
>
> Show some basic initiative.  Look around.  Show us what abnormal things
> are going on with your system.
>
> ls -ld / /etc /etc/ld.*
> strace /sbin/ldconfig
>
> Do something, do ANYTHING useful!
>
Thank you for your helpful comment.  Unfortunately. I am an Organioc 
Chemist, not an IT person. Therefore, I am only a user.

Now, strace is not installed, nor can I install it, thanks to the error 
messages.

Might this help?

root@AbNormal:/home/comp# ls -ld / /etc /etc/ld.*
drwxr-xr-x  26 root root   4096 Dec 19 13:17 /
drwxr-xr-x 134 root root  12288 Jan  3 09:43 /etc
-rw-r--r--   1 root root 237114 Dec 26 14:47 /etc/ld.so.cache
-rw-------   1 root root  12288 Jan  3 12:49 /etc/ld.so.cache~
-rw-r--r--   1 root root     34 Apr  9  2017 /etc/ld.so.conf
drwxr-xr-x   2 root root   4096 Aug 22 07:41 /etc/ld.so.conf.d

-- 
Stephen P. Molnar, Ph.D.
Consultant
www.molecular-modeling.net
(614)312-7528 (c)
Skype: smolnar1

[toc] | [prev] | [next] | [standalone]

#203895

On Thu, Jan 03, 2019 at 02:42:50PM -0500, Greg Wooledge wrote:
> When I run "strace /sbin/ldconfig" on my system, I see this line:
> 
> rename("/etc/ld.so.cache~", "/etc/ld.so.cache") = 0

Oh, and there was also this stuff:

stat("/var/cache/ldconfig", {st_mode=S_IFDIR|0700, st_size=4096, ...}) = 0
open("/var/cache/ldconfig/aux-cache~", O_WRONLY|O_CREAT|O_TRUNC|O_NOFOLLOW, 0600) = 3
write(3, "glibc-ld.so.auxcache-1.0\273\2\0\0\376-\0\0"..., 45358) = 45358
close(3)                                = 0
rename("/var/cache/ldconfig/aux-cache~", "/var/cache/ldconfig/aux-cache") = 0
brk(0xa2d000)                           = 0xa2d000

Maybe your /var/cache/ldconfig directory is missing?  I honestly have
no idea what that is.  I've never seen it before.

[toc] | [prev] | [next] | [standalone]

#203896

On Thu, Jan 03, 2019 at 02:30:49PM -0500, Stephen P. Molnar wrote:
> root@AbNormal:/home/comp# ls -ld / /etc /etc/ld.*
> drwxr-xr-x  26 root root   4096 Dec 19 13:17 /
> drwxr-xr-x 134 root root  12288 Jan  3 09:43 /etc
> -rw-r--r--   1 root root 237114 Dec 26 14:47 /etc/ld.so.cache
> -rw-------   1 root root  12288 Jan  3 12:49 /etc/ld.so.cache~
> -rw-r--r--   1 root root     34 Apr  9  2017 /etc/ld.so.conf
> drwxr-xr-x   2 root root   4096 Aug 22 07:41 /etc/ld.so.conf.d

Well... /etc isn't missing, at least.

When I run "strace /sbin/ldconfig" on my system, I see this line:

rename("/etc/ld.so.cache~", "/etc/ld.so.cache") = 0

So, it seems that your ldconfig is generating the /etc/ld.so.cache~ file,
or at least a partial one (12288 is a suspiciously ROUND number, being
precisely 3 times 4 kilobytes).  And then ... something bad happens before
it can rename it to /etc/ld.so.cache.  Or finish writing it.

Are you out of disk space?  Granted, I would have expected a DIFFERENT
error message in that case, but it's a thing to check.

You might consider simply copying the /usr/bin/strace file from a
different Debian system onto this one, just so you can run it.

[toc] | [prev] | [next] | [standalone]

#203903

On 01/03/2019 02:42 PM, Greg Wooledge wrote:
> On Thu, Jan 03, 2019 at 02:30:49PM -0500, Stephen P. Molnar wrote:
>> root@AbNormal:/home/comp# ls -ld / /etc /etc/ld.*
>> drwxr-xr-x  26 root root   4096 Dec 19 13:17 /
>> drwxr-xr-x 134 root root  12288 Jan  3 09:43 /etc
>> -rw-r--r--   1 root root 237114 Dec 26 14:47 /etc/ld.so.cache
>> -rw-------   1 root root  12288 Jan  3 12:49 /etc/ld.so.cache~
>> -rw-r--r--   1 root root     34 Apr  9  2017 /etc/ld.so.conf
>> drwxr-xr-x   2 root root   4096 Aug 22 07:41 /etc/ld.so.conf.d
> Well... /etc isn't missing, at least.
>
> When I run "strace /sbin/ldconfig" on my system, I see this line:
>
> rename("/etc/ld.so.cache~", "/etc/ld.so.cache") = 0
>
> So, it seems that your ldconfig is generating the /etc/ld.so.cache~ file,
> or at least a partial one (12288 is a suspiciously ROUND number, being
> precisely 3 times 4 kilobytes).  And then ... something bad happens before
> it can rename it to /etc/ld.so.cache.  Or finish writing it.
>
> Are you out of disk space?  Granted, I would have expected a DIFFERENT
> error message in that case, but it's a thing to check.
>
> You might consider simply copying the /usr/bin/strace file from a
> different Debian system onto this one, just so you can run it.
>
OK.  I happen to have Debian Stretch in a virtual machine for testing 
purposes.

strace is in /usr/bin on there.  I copied it to the host and ran it.

comp@AbNormal:~$ sudo ./strace
[sudo] password for comp:
./strace: must have PROG [ARGS] or -p PID
Try './strace -h' for more information.

I'm totally at sea here, which switch should iI use?

Also:

comp@AbNormal:~$ df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            3.9G     0  3.9G   0% /dev
tmpfs           789M   18M  772M   3% /run
/dev/sda1        23G   23G     0 100% /                   <- could this 
e a problem?
tmpfs           3.9G   12K  3.9G   1% /dev/shm
tmpfs           5.0M  8.0K  5.0M   1% /run/lock
tmpfs           3.9G     0  3.9G   0% /sys/fs/cgroup
/dev/sda7       1.9G  6.5M  1.7G   1% /tmp
/dev/sda5       9.2G  6.0G  2.8G  69% /var
/dev/sda8       416G  103G  292G  27% /home
/dev/sdc1        20G  301M   19G   2% /sdc1
/dev/sdc2       439G  169G  270G  39% /sdc2
/dev/sdb1       1.8T  288G  1.5T  17% /sdb1
tmpfs           789M  4.0K  789M   1% /run/user/110
tmpfs           789M   28K  789M   1% /run/user/1000

I have all of my application software in /home/comp/Apps

-- 
Stephen P. Molnar, Ph.D.
Consultant
www.molecular-modeling.net
(614)312-7528 (c)
Skype: smolnar1

[toc] | [prev] | [next] | [standalone]

#203904

Stephen P. Molnar wrote:

> strace is in /usr/bin on there.  I copied it to the host and ran it.
> 
> comp@AbNormal:~$ sudo ./strace
> [sudo] password for comp:
> ./strace: must have PROG [ARGS] or -p PID
> Try './strace -h' for more information.
> 
> I'm totally at sea here, which switch should iI use?

You don't just copy executables here and there (unless instructed to do so)
You install via package manager

        sudo apt-get install strace

usually linux programs (installed the proper way) come with man(ual) page,
so

        man strace

will help you understand how the program can be run and of course you have
google or a like

you run strace with the executable you want to trace

        sudo strace ldconfig

regards

[toc] | [prev] | [next] | [standalone]

#203907

[Multipart message — attachments visible in raw view] — view raw

deloptes (2019-01-03):
> You don't just copy executables here and there (unless instructed to do so)
> You install via package manager

Could you please read the mails you are answering to before spewing
unhelpful comments?

Thanks in advance.

-- 
  Nicolas George

[toc] | [prev] | [next] | [standalone]

#203913

Nicolas George wrote:

> Could you please read the mails you are answering to before spewing
> unhelpful comments?

Next time please explain ... not that I did not understand what you mean,
but it sounds very personal.
You could just point out, that it is not possible to install package when
the installer has unconfigured libc-bin package.

I think we found the problem few mails below.

regards

[toc] | [prev] | [next] | [standalone]

#203943

Hi Stephen,

Stephen P. Molnar:
> 
> 
> On 01/03/2019 02:42 PM, Greg Wooledge wrote:
>> On Thu, Jan 03, 2019 at 02:30:49PM -0500, Stephen P. Molnar wrote:
>>> root@AbNormal:/home/comp# ls -ld / /etc /etc/ld.*
>>> drwxr-xr-x  26 root root   4096 Dec 19 13:17 /
>>> drwxr-xr-x 134 root root  12288 Jan  3 09:43 /etc
>>> -rw-r--r--   1 root root 237114 Dec 26 14:47 /etc/ld.so.cache
>>> -rw-------   1 root root  12288 Jan  3 12:49 /etc/ld.so.cache~
>>> -rw-r--r--   1 root root     34 Apr  9  2017 /etc/ld.so.conf
>>> drwxr-xr-x   2 root root   4096 Aug 22 07:41 /etc/ld.so.conf.d
>> Well... /etc isn't missing, at least.
>>
>> When I run "strace /sbin/ldconfig" on my system, I see this line:
>>
>> rename("/etc/ld.so.cache~", "/etc/ld.so.cache") = 0
>>
>> So, it seems that your ldconfig is generating the /etc/ld.so.cache~ file,
>> or at least a partial one (12288 is a suspiciously ROUND number, being
>> precisely 3 times 4 kilobytes).  And then ... something bad happens 
>> before
>> it can rename it to /etc/ld.so.cache.  Or finish writing it.
>>
>> Are you out of disk space?  Granted, I would have expected a DIFFERENT
>> error message in that case, but it's a thing to check.
>>
>> You might consider simply copying the /usr/bin/strace file from a
>> different Debian system onto this one, just so you can run it.
>>
> OK.  I happen to have Debian Stretch in a virtual machine for testing 
> purposes.
> 
> strace is in /usr/bin on there.  I copied it to the host and ran it.
> 
> comp@AbNormal:~$ sudo ./strace
> [sudo] password for comp:
> ./strace: must have PROG [ARGS] or -p PID
> Try './strace -h' for more information.
> 
> I'm totally at sea here, which switch should iI use?
> 
> Also:
> 
> comp@AbNormal:~$ df -h
> Filesystem      Size  Used Avail Use% Mounted on
> udev            3.9G     0  3.9G   0% /dev
> tmpfs           789M   18M  772M   3% /run
> /dev/sda1        23G   23G     0 100% /                   <- could this 
> e a problem?
> tmpfs           3.9G   12K  3.9G   1% /dev/shm
> tmpfs           5.0M  8.0K  5.0M   1% /run/lock
> tmpfs           3.9G     0  3.9G   0% /sys/fs/cgroup
> /dev/sda7       1.9G  6.5M  1.7G   1% /tmp
> /dev/sda5       9.2G  6.0G  2.8G  69% /var
> /dev/sda8       416G  103G  292G  27% /home
> /dev/sdc1        20G  301M   19G   2% /sdc1
> /dev/sdc2       439G  169G  270G  39% /sdc2
> /dev/sdb1       1.8T  288G  1.5T  17% /sdb1
> tmpfs           789M  4.0K  789M   1% /run/user/110
> tmpfs           789M   28K  789M   1% /run/user/1000
> 
> I have all of my application software in /home/comp/Apps
> 

Your root partition is out of space,>> /dev/sda1        23G   23G     0 
100% /                   <- could this
  so there won't be any writing to /etc , which is on this partition, 
until You get rid of some data, e.g. in /root.

Then try again, what You've been told in this thread.

kind regards

readU
Frank

[toc] | [prev] | [next] | [standalone]

#203908

On 01/03/2019 03:31 PM, Nicolas George wrote:
> Stephen P. Molnar (2019-01-03):
>> Thank you for your helpful comment.  Unfortunately. I am an Organioc
>> Chemist, not an IT person. Therefore, I am only a user.
> Then ask your sysadmin.
>
> Regards,
>
I have no sysadmin.

-- 
Stephen P. Molnar, Ph.D.
Consultant
www.molecular-modeling.net
(614)312-7528 (c)
Skype: smolnar1

[toc] | [prev] | [next] | [standalone]

#203914

[Multipart message — attachments visible in raw view] — view raw

Stephen P. Molnar (2019-01-03):
> > > Thank you for your helpful comment.  Unfortunately. I am an Organioc
> > > Chemist, not an IT person. Therefore, I am only a user.

> > Then ask your sysadmin.

> I have no sysadmin.

Then you are not "only a user", you are a sysadmin, and you are trying
to be one without acquiring the required knowledge.

Regards,

-- 
  Nicolas George

[toc] | [prev] | [next] | [standalone]

#203917

On Thu, Jan 03, 2019 at 10:27:30PM +0100, Nicolas George wrote:
> Stephen P. Molnar (2019-01-03):
> > > > Thank you for your helpful comment.  Unfortunately. I am an Organioc
> > > > Chemist, not an IT person. Therefore, I am only a user.
> 
> > > Then ask your sysadmin.
> 
> > I have no sysadmin.
> 
> Then you are not "only a user", you are a sysadmin, and you are trying
> to be one without acquiring the required knowledge.
> 
That would be like saying that someone who operates a motor vehicle
without also being a mechanic is doing so without acquiring the required
knowlege.  It is not reasonable to expect that everybody will learn to
be a system administrator in order to use a computer.  In Stephen's
case, the computer is a tool he uses to get his job done.

I see no problem with him focusing on his job instead of learning to be
a sysadmin.  In this case, he encountered a problem, came here for help
and several people were able to help him diagnose the problem and start
moving toward a solution.

It seems like it worked out for all involved.

Regards,

-Roberto

-- 
Roberto C. Sánchez

[toc] | [prev] | [next] | [standalone]

Page 1 of 5  [1] 2 3 4 5  Next page →

Back to top | Article view | linux.debian.user

csiph-web