Bug#839880: proftpd-basic: proftpd server instance crashed with signal 11

[Мороз Олег]

Hi,


Have made changes in

/etc/security/limits.d/core_dump.conf

then set path to save code dumps into /tmp

vniiem at sim-ng-data /tmp % /sbin/sysctl -a -r kernel.core
kernel.core_pattern = /tmp/core.%e.%p.%t
kernel.core_pipe_limit = 0
kernel.core_uses_pid = 0

Then relogin and reinstall proftpd, tried to login to ftp , but no 
core.dump was generated



25.12.2017 17:09, Hilmar Preuße пишет:
> On 24.12.2017 11:32, Олег Мороз wrote:
>
> Hi,
>
> no, we did not package any version between b-4 and d-1. However I doubt
> to learn a lot by simply knowing in which version the issue was introduced.
>
> Regarding your core dumps: Please make sure the core dumps are created
> in the context of every user:
>
> hille at haka:~$ less -X /etc/security/limits.d/core_dump.conf
> # Each line describes a limit for a user in the form:
> #
> # <domain> <type> <item> <value>
> #
> *  hard  core  unlimited
> *  soft  core  unlimited
>
> ...or set it directly in the limits.conf. Settings are effective upon
> next login.
>
> If your system is configured to write core dumps to a specific location:
>
> hille at haka:~$ /sbin/sysctl -a -r kernel.core
> kernel.core_pattern = /var/crash/core.%e.%p.%h.%t
> kernel.core_pipe_limit = 0
> kernel.core_uses_pid = 0
> hille at haka:~$
>
> ...make sure it is writable for the specific user: proftp runs as user
> proftpd . Make it world writable for now.
>
> Hilmar
>
>> I'm not checked any version except 1.3.5b-4 and 1.3.5d-1. If it possible
>> to download .deb packages for any other version within that interval,
>> i'll be happy to test it.
>>
>> 24.12.2017 12:21, Hilmar Preuße пишет:
>>> Am 24.12.2017 um 08:33 teilte Олег Мороз mit:
>>>
>>> Hi Олег,
>>>
>>> so, your problem was introduced anywhere between 1.3.5b & 1.3.5d?
>>>
>>> You can have a look at the files in /usr/share/doc/proftpd-basic/ here
>>> are the upstream logs (changelog.gz) and the Debian Log. However I
>>> don't think that they are useful to debug your problem.
>>>
>>> Hilmar
>>>
>>>>   >does http://bugs.proftpd.org/show_bug.cgi?id=4321 eventually
>>>> describe your problem?
>>>> Don't think so. Have tried to disable pam, but with no effect. Anyway
>>>> i've reinstall proftpd-basic 1.3.5b-4 from stretch - looks to be work.
>>>>
>>>> Where can i find information about changes from 1.3.5b-4 up to 1.3.5d-1?
>>>>

-- 
Олег Мороз
Заместитель начальника отдела АО "Корпорация ВНИИЭМ"
+7-963-760-70-15