-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry about late reply, got a bit busy with other things.
On 11/07/2014 11:43 PM, Reco wrote:
> Hi.
>
> I'd try adding some memory (or swapspace) to this VM to satisfy
> mremap's wish to remap to exactly 8G virtual memory.
>
> Reco
Tried this, set
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/09/2014 12:55 PM, Don Armstrong wrote:
> On Sun, 09 Nov 2014, Joris Bolsens wrote:
>> Where do i find the object file for libnss-ldap? I tried running
>> nm -a on pretty much every file I could find with libnss-ldap in
>> the name and it said
On Sun, 09 Nov 2014, Joris Bolsens wrote:
> Where do i find the object file for libnss-ldap? I tried running nm -a
> on pretty much every file I could find with libnss-ldap in the name
> and it said it didn't recognize the file type.
It should be symlinked from /lib64/libnss_ldap.so.2 or
/lib/x86_
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/08/2014 03:43 PM, Don Armstrong wrote:
> No, just don't send the whole core dump itself (the file called
> core) to the BTS (or this mailing list). It almost certainly has
> your machine ldap password in it.
that makes sense, wont do that, tha
On Sat, 08 Nov 2014, Joris Bolsens wrote:
> Not sure what you mean by this, don't post the full output of the
> command?
No, just don't send the whole core dump itself (the file called core) to
the BTS (or this mailing list). It almost certainly has your machine
ldap password in it.
On Sat, 08 No
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/08/2014 12:16 PM, Don Armstrong wrote:
> apt-get build-dep libnss-ldap; DEB_BUILD_OPTS="nostrip,noopt"
> apt-get source -b libnss-ldap;
>
> will give you those symbols.
>
> Then you can rerun /usr/sbin/useradd foo; and re-analyze the
> cored
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/08/2014 12:16 PM, Don Armstrong wrote:
> Please double check the bt full; output for any obvious password
> strings too before posting to this mailing list. [I should have
> told you to do that too, but I don't see any below, so you should
> b
On Sat, 08 Nov 2014, Joris Bolsens wrote:
> I can't be 100% certain because I'm not sure what any of this means,
> but it would seem I messed up somewhere as it shows `No Symbol Table
> info available` for libnss_ldap.
Awesome. It looks like it's segfaulting in libnss_ldap, which you didn't
build
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I can't be 100% certain because I'm not sure what any of this means,
but it would seem I messed up somewhere as it shows `No Symbol Table
info available` for libnss_ldap.
This bit also seems possibly problematic
`warning: Can't read pathname for load
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/08/2014 11:16 AM, Don Armstrong wrote:
> ulimit -c unlimited; useradd foo; gdb /usr/sbin/useradd core; bt
> full; or similar.
>
> You'll also want to install libc6-dbg gdb; and similar.
>
> This will give you an idea of where the code is seg
On Sat, 08 Nov 2014, Joris Bolsens wrote:
> Sorry, pretty new to linux still. put a few questions in-line.
No worries.
> On 11/08/2014 09:39 AM, Don Armstrong wrote:
>
> > Before filing a bug, please
> >
> > 1) Enable coredumps
> Did some googling, I have to recompile the kernel for this?
> th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry, pretty new to linux still. put a few questions in-line.
On 11/08/2014 09:39 AM, Don Armstrong wrote:
> Before filing a bug, please
>
> 1) Enable coredumps
Did some googling, I have to recompile the kernel for this?
the one thing i did find
On Fri, 07 Nov 2014, Joris Bolsens wrote:
> Ran into a bit of a strange error with useradd today, whenever i run
> useradd I get a Segmentation fault.
Before filing a bug, please
1) Enable coredumps
2) Get a coredump
3) Backtrace it
4) Install any missing -dbg packages which provide symbols for t
Hi.
On Sat, 08 Nov 2014 01:02:25 -0800
Joris Bolsens wrote:
>> >
> > So, chances are - you've found a bug.
> >
> Awesome, where/how should I report it?
Install reportbug package. Invoke 'reportbug passwd'.
The rest of the process will be explained to you by the reportbug.
Reportbug requires
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/07/2014 11:43 PM, Reco wrote:
>
> So, chances are - you've found a bug.
>
Awesome, where/how should I report it?
>
>> and memory info on top:
>>
>> KiB Mem: 2061128 total, 263680 used, 1797448 free,75180
>> buffers KiB Swap: 20
Hi.
On Fri, 07 Nov 2014 18:04:25 -0800
Joris Bolsens wrote:
> mremap(0x7f239914d000, 4294971392, 8589938688, MREMAP_MAYMOVE) = -1 EFAULT
> (Bad address)
It goes downhill from here. Apparently useradd does not checks a return
status of mremap, and, according to the mremap(2), EFAULT is define
On 11/07/2014 11:29 PM, Joris Bolsens wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
No idea, that's just what i got when I ran the command, I left out a
bit at the top that did the ldap lookups, that all looked find and
didn't want to include that as 1) dont think it's relevant and 2)
con
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
No idea, that's just what i got when I ran the command, I left out a
bit at the top that did the ldap lookups, that all looked find and
didn't want to include that as 1) dont think it's relevant and 2)
contains some sensitive data (usernames and such),
On 11/07/2014 09:04 PM, Joris Bolsens wrote:
Ran into a bit of a strange error with useradd today,
whenever i run useradd I get a Segmentation fault.
I tried running fsck as i read it might be due to corrupt filesystem, but that
didn't report any problems.
I reinstalled the passwd package, also
it seems that using the adduser works fine, not sure why i didn't think to try
that before.
However I am still curious why this occurred.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http
Ran into a bit of a strange error with useradd today,
whenever i run useradd I get a Segmentation fault.
I tried running fsck as i read it might be due to corrupt filesystem, but that
didn't report any problems.
I reinstalled the passwd package, also to no avail.
I ran an strace and it seems it
21 matches
Mail list logo
