Yes. I see the same problem. It appears the problem is because the Proftpd service is not completely started when the wizard tests for success. The next time the wizard is run the service is already started so the test succeeds.


Looking at /usr/lib/perl5/vendor_perl/5.12.3/MDK/Wizard/Proftpd.pm at the end of the file the Proftpd service is started by a call to services::start('proftpd')
Immediately after a check is made on the existence of the pid.

To prove it is a timing issue, if a put a delay in before testing then the wizard works first time.

From line number 322

    if (services::is_service_running('proftpd')) {
        services::restart('proftpd');
    } else {
        services::start('proftpd');
    }
    sleep 2;
    check_started('proftpd');
}

1;

CC: (none) => derekjenn

I think I may have a proper fix.

In /usr/lib/perl5/vendor_perl/5.12.3/MDK/Wizard/Wizcommon.pm around line 46

sub check_started {
  my ($service) = @_;
#  my ($isrunning) = chomp_(`pidof $service`) =~ /(\d+)/m;
  my ($isrunning) = services::is_service_running('$service');
  if (!$isrunning) {
    return 'error_end';
  }
}

This bug probably affects all the other wizards too since they all have similar status checks.

Thanks for all your work

Makes me feel good that we found something
that looks insignificant but effects lots
of things other then the FTP install.

Yeah this is likely due to the non-blocking mode put into service starting (which is needed to avoid transaction deadlocks when run at boot.

There are a couple cases where blocking is needed in the UI, so I guess we need to ensure we only use non-blocking mode on boot :s

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Still valid for Mageia 2

Version: Cauldron => 2

Ya, I would say it's still valid for M2

This bug is still valid for me in M3A2 on
10/15/12 using boot.iso 10/02/12 32-bit

Applied to SVN after fixing it

Status: NEW => RESOLVED
Resolution: (none) => FIXED