Project

General

Profile

Bug #25963

proftp does not start up

Added by Simon Englisch almost 3 years ago. Updated over 2 years ago.

Status:
Closed: Insufficient Info
Priority:
No priority
Assignee:
Release Council
Category:
OS
Target version:
Severity:
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:

HP ProLiant N40L Microserver
16 GB Ram
3 x 3 TB Western Digital Red

ChangeLog Required:
No

Description

Since the latest 11-Nightlys-Update FTP service on my machine is dead - does not start up.

root@freenas:~ # /usr/local/etc/rc.d/proftpd start
Starting proftpd.
2017-09-24 16:16:39,467 freenas.local proftpd[3809]: -----BEGIN STACK TRACE-----
2017-09-24 16:16:39,467 freenas.local proftpd[3809]: [0] 0x801856934 <pthread_sigmask+0x544> at /lib/libthr.so.3
2017-09-24 16:16:39,467 freenas.local proftpd[3809]: [1] 0x801855ecf <pthread_getspecific+0xe5f> at /lib/libthr.so.3
2017-09-24 16:16:39,467 freenas.local proftpd[3809]: -----END STACK TRACE-----
2017-09-24 16:16:39,467 freenas.local proftpd[3809]: ProFTPD terminating (signal 11)
2017-09-24 16:16:39,467 freenas.local proftpd[3809]: ProFTPD terminating (signal 11)
2017-09-24 16:16:39,467 freenas.local proftpd[3809]: ProFTPD 1.3.6 standalone mode SHUTDOWN
/usr/local/etc/rc.d/proftpd: WARNING: failed to start proftpd


Related issues

Related to FreeNAS - Bug #27801: Problem with FTP access after 11.1 UpgradeClosed
Related to FreeNAS - Bug #27670: Update proftpdClosed

History

#1 Updated by Simon Englisch almost 3 years ago

I did not change any settings in the web GUI since then.
Also trying to start proftpd generates no log except WARNING: failed to start proftpd, so I don't know what information else would help.

#2 Updated by Dru Lavigne almost 3 years ago

  • Status changed from Unscreened to 15

Do you get the same error on the latest 11 STABLE? Nightlies are meant for testing purposes only and may have some type of brokenness at any point in time.

#3 Updated by Simon Englisch almost 3 years ago

I tried to revert to stable, but this fucked the system totally, so I do not know.
I understood that nightlies are for testing - so I stay with "testing showed that ftp is broken" :-)

#4 Updated by Dru Lavigne almost 3 years ago

How did you revert? With a fresh install and config? You can't reuse a later (eg nightly) config on a stable install, but you can reboot into either, once they are configured (a stable config on a stable build and a nightly config on a nightly build).

#5 Updated by Dru Lavigne almost 3 years ago

  • Status changed from 15 to Closed: Insufficient Info
  • Target version set to N/A

#6 Updated by Francesco Pantz over 2 years ago

Dru Lavigne wrote:

How did you revert? With a fresh install and config? You can't reuse a later (eg nightly) config on a stable install, but you can reboot into either, once they are configured (a stable config on a stable build and a nightly config on a nightly build).

sorry to open an old bug, but since i upgraded to 11.1 Release, i get this error when i try FTP access to my nas through Filezilla (it always worked before)

Jan 15 13:01:07 freenas proftpd[68741]: localhost - -----BEGIN STACK TRACE-----
Jan 15 13:01:07 freenas proftpd[68741]: localhost - [0] 0x801855904 <pthread_sigmask+0x544> at /lib/libthr.so.3
Jan 15 13:01:07 freenas proftpd[68741]: localhost - [1] 0x801854e9f <pthread_getspecific+0xe2f> at /lib/libthr.so.3
Jan 15 13:01:07 freenas proftpd[68741]: localhost - -----END STACK TRACE-----

Is it releted?

#7 Updated by Dru Lavigne over 2 years ago

Francesco: please create a new ticket that includes a debug (System -> Advanced -> Save Debug) from your system.

#8 Updated by Simon Englisch over 2 years ago

  • File debug-freenas-20180115213825.tgz added
  • Seen in changed from Master - FreeNAS Nightlies to Master - FreeBSD-Stable

I too have this problem again (after my first ticket was refused by handwaving and "it's a nightly, so don't complain").
Now I am on 11-stable.

Just restarted my machine after it was completely stuck by running out of swap.

This is what I have in my log right after the restart:

Jan 15 21:22:21 freenas proftpd[6876]: localhost - -----BEGIN STACK TRACE-----
Jan 15 21:22:21 freenas proftpd[6876]: localhost - [0] 0x801855904 <pthread_sigmask+0x544> at /lib/libthr.so.3
Jan 15 21:22:21 freenas proftpd[6876]: localhost - [1] 0x801854e9f <pthread_getspecific+0xe2f> at /lib/libthr.so.3
Jan 15 21:22:21 freenas proftpd[6876]: localhost - -----END STACK TRACE-----
Jan 15 21:22:21 freenas proftpd[6876]: localhost - ProFTPD terminating (signal 11)
Jan 15 21:22:23 freenas proftpd[6878]: localhost - -----BEGIN STACK TRACE-----
Jan 15 21:22:23 freenas proftpd[6878]: localhost - [0] 0x801855904 <pthread_sigmask+0x544> at /lib/libthr.so.3
Jan 15 21:22:23 freenas proftpd[6878]: localhost - [1] 0x801854e9f <pthread_getspecific+0xe2f> at /lib/libthr.so.3
Jan 15 21:22:23 freenas proftpd[6878]: localhost - -----END STACK TRACE-----
Jan 15 21:22:23 freenas proftpd[6878]: localhost - ProFTPD terminating (signal 11)
Jan 15 21:22:23 freenas proftpd[6879]: localhost - -----BEGIN STACK TRACE-----
Jan 15 21:22:23 freenas proftpd[6879]: localhost - [0] 0x801855904 <pthread_sigmask+0x544> at /lib/libthr.so.3
Jan 15 21:22:23 freenas proftpd[6879]: localhost - [1] 0x801854e9f <pthread_getspecific+0xe2f> at /lib/libthr.so.3
Jan 15 21:22:23 freenas proftpd[6879]: localhost - -----END STACK TRACE-----
Jan 15 21:22:23 freenas proftpd[6879]: localhost - ProFTPD terminating (signal 11)
Jan 15 21:22:38 freenas proftpd[6881]: localhost - -----BEGIN STACK TRACE-----
Jan 15 21:22:38 freenas proftpd[6881]: localhost - [0] 0x801855904 <pthread_sigmask+0x544> at /lib/libthr.so.3
Jan 15 21:22:38 freenas proftpd[6881]: localhost - [1] 0x801854e9f <pthread_getspecific+0xe2f> at /lib/libthr.so.3
Jan 15 21:22:38 freenas proftpd[6881]: localhost - -----END STACK TRACE-----
Jan 15 21:22:38 freenas proftpd[6881]: localhost - ProFTPD terminating (signal 11)
Jan 15 21:23:01 freenas proftpd[6952]: localhost - -----BEGIN STACK TRACE-----
Jan 15 21:23:01 freenas proftpd[6952]: localhost - [0] 0x801855904 <pthread_sigmask+0x544> at /lib/libthr.so.3
Jan 15 21:23:01 freenas proftpd[6952]: localhost - [1] 0x801854e9f <pthread_getspecific+0xe2f> at /lib/libthr.so.3
Jan 15 21:23:01 freenas proftpd[6952]: localhost - -----END STACK TRACE-----
Jan 15 21:23:01 freenas proftpd[6952]: localhost - ProFTPD terminating (signal 11)
Jan 15 21:23:03 freenas daemon[2898]:     2018/01/15 21:23:03 [WARN] agent: Check 'service:nas-health' is now warning
Jan 15 21:23:21 freenas proftpd[7010]: localhost - -----BEGIN STACK TRACE-----
Jan 15 21:23:21 freenas proftpd[7010]: localhost - [0] 0x801855904 <pthread_sigmask+0x544> at /lib/libthr.so.3
Jan 15 21:23:21 freenas proftpd[7010]: localhost - [1] 0x801854e9f <pthread_getspecific+0xe2f> at /lib/libthr.so.3
Jan 15 21:23:21 freenas proftpd[7010]: localhost - -----END STACK TRACE-----
Jan 15 21:23:21 freenas proftpd[7010]: localhost - ProFTPD terminating (signal 11)

#9 Updated by Dru Lavigne over 2 years ago

  • Related to Bug #27801: Problem with FTP access after 11.1 Upgrade added

#10 Updated by Dru Lavigne over 2 years ago

#11 Updated by Dru Lavigne over 2 years ago

  • File deleted (debug-freenas-20180115213825.tgz)

#12 Updated by Dru Lavigne over 2 years ago

Simon: I deleted your debug as there are currently 2 related tickets being investigated. Note that you may not be able to see those tickets yet (they are hidden while they still contain a user's debug).

#13 Updated by Simon Englisch over 2 years ago

Thanks for this info

Also available in: Atom PDF