Re: [Spacewalk-devel] 0.5 State of the Union
On Wednesday 25 March 2009 17:00:37 Devan Goodwin wrote: dgilmore fixed up our jabber configs to work on 2.2 yesterday, so updated spacewalk-config and spacewalk-setup packages correct this, but you probably need to be on a fresh system before it will work. (i.e. not a system where you tried and failed to setup spacewalk, not sure why but Dennis can probably clarify) With these fixes in place -- does /var/log/rhn/osa-dispatcher.log on your new 0.5 installation look OK? -MZ ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] 0.5 State of the Union
On Thu, Mar 26, 2009 at 09:32:44PM -0400, Jesus M. Rodriguez wrote: Jan please look at this bug: https://bugzilla.redhat.com/show_bug.cgi?id=492194 After long investigation, I've filed bugzilla 492378 for that. I'll try to find a way to work around the problem tomorrow. Ok that would be great. Done. I've built spacewalk-setup-0.5.27-1.fc10.noarch.rpm, please give it a try. -- Jan Pazdziora Senior Software Engineer, Satellite Engineering, Red Hat ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] 0.5 State of the Union
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 27 Mar 2009 12:00:40 +0100 Jan Pazdziora jpazdzi...@redhat.com wrote: On Thu, Mar 26, 2009 at 09:32:44PM -0400, Jesus M. Rodriguez wrote: Jan please look at this bug: https://bugzilla.redhat.com/show_bug.cgi?id=492194 After long investigation, I've filed bugzilla 492378 for that. I'll try to find a way to work around the problem tomorrow. Ok that would be great. Done. I've built spacewalk-setup-0.5.27-1.fc10.noarch.rpm, please give it a try. Tested and looking good on F10, I'll hit CentOS 5 soon as I can wrap up this other issue blocking it. Thanks Jan. Devan - -- Devan Goodwin dgood...@redhat.com Software Engineer Spacewalk / RHN Satellite Halifax, Canada 650.567.9039x79267 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAknMxjUACgkQAyHWaPV9my4PmwCguq/bdtrO2rmtNPAxg0ZDdO3i 4LcAn0Ci73IOB8+5y5CrA5sNe8JMq+Xw =ITJU -END PGP SIGNATURE- ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] 0.5 State of the Union
On Thu, Mar 26, 2009 at 1:03 PM, Jan Pazdziora jpazdzi...@redhat.com wrote: On Wed, Mar 25, 2009 at 05:26:16PM -0400, Jesus M. Rodriguez wrote: IIRC you never get past the waidpid. It is noteworthy that everything is up and running at this point, spacewalk-setup just doesn't realize it. Jan please look at this bug: https://bugzilla.redhat.com/show_bug.cgi?id=492194 After long investigation, I've filed bugzilla 492378 for that. I'll try to find a way to work around the problem tomorrow. Ok that would be great. jesus ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] 0.5 State of the Union
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
dgilmore fixed up our jabber configs to work on 2.2 yesterday, so
updated spacewalk-config and spacewalk-setup packages correct this, but
you probably need to be on a fresh system before it will work. (i.e.
not a system where you tried and failed to setup spacewalk, not sure
why but Dennis can probably clarify)
Issue found and fixed this morning with regexps in ssl.conf that was
causing httpd to refuse to start, Milan fixed up and rebuilt
spacewalk-setup-0.5.25.
spacewalk-backend also rebuilt this morning to pickup the rhnpush fix
jbowes submitted.
These should all be appearing in the devel repo soon, I think we
updated it 4x daily.
On Fedora 10 I see two issues,
spacewalk-setup still hangs at the end restarting services. Everything
seems to be up and running fine including jabberd, I think the problem
is jabberd printing something to stdout/stderr that's messing with the
way we intercept output and log it to rhn-installation.log. If you
switch to another terminal and run service jabberd restart,
spacewalk-setup immediately picks back up and completes. If you trace
this down I believe you land in Setup.pm sub system_debug:
while (PROCESS_OUT) {
print LOGFILE $_;
}
waitpid($pid, 0);
IIRC you never get past the waidpid. It is noteworthy that everything
is up and running at this point, spacewalk-setup just doesn't realize
it.
There's also a lesser problem causing these lines to be printed during
spacewalk-setup:
Use of uninitialized value $uid in chown
at /usr/bin/rhn-generate-pem.pl line 74.
Use of uninitialized value $gid in chown
at /usr/bin/rhn-generate-pem.pl line 74.
This is because we try to change permissions on a file to be owned by
the jabberd user, which doesn't exist at least on F10, it's now just
the jabber user.
Devan
- --
Devan Goodwin dgood...@redhat.com
Software Engineer Spacewalk / RHN Satellite
Halifax, Canada 650.567.9039x79267
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.9 (GNU/Linux)
iEYEARECAAYFAknKVSkACgkQAyHWaPV9my5LHACdHmlczPWPGyWj8B5tDe+Y2NSC
3v4AoJzsDrwwo/hS89IOghMOSKSOI8fG
=pNqG
-END PGP SIGNATURE-
___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] 0.5 State of the Union
On Wednesday 25 March 2009 11:00:37 am Devan Goodwin wrote: dgilmore fixed up our jabber configs to work on 2.2 yesterday, so updated spacewalk-config and spacewalk-setup packages correct this, but you probably need to be on a fresh system before it will work. (i.e. not a system where you tried and failed to setup spacewalk, not sure why but Dennis can probably clarify) the issue was that there were inconsistent passwords in jabber config files. jabberd randomly generates a password in %post so we cantdefault ours. we write out our own randomly generated password when we install the package. but you really don't want updates to mess with it. so it only happens on package install. a less hackish way to deal with it would be to generate the password in spacewalk-setup and write it out to the configs when you setup spacewalk. this would involve alot more work but ultimately would be cleaner, its something we should look at post 0.5 Dennis signature.asc Description: This is a digitally signed message part. ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] 0.5 State of the Union
2009/3/25 Dennis Gilmore den...@ausil.us: On Wednesday 25 March 2009 11:00:37 am Devan Goodwin wrote: dgilmore fixed up our jabber configs to work on 2.2 yesterday, so updated spacewalk-config and spacewalk-setup packages correct this, but you probably need to be on a fresh system before it will work. (i.e. not a system where you tried and failed to setup spacewalk, not sure why but Dennis can probably clarify) the issue was that there were inconsistent passwords in jabber config files. jabberd randomly generates a password in %post so we cantdefault ours. we write out our own randomly generated password when we install the package. but you really don't want updates to mess with it. so it only happens on package install. a less hackish way to deal with it would be to generate the password in spacewalk-setup and write it out to the configs when you setup spacewalk. this would involve alot more work but ultimately would be cleaner, its something we should look at post 0.5 Hmmm if spacewalk had a 'puppet' like tool then the first node it could configure would be itself and that would be where to put that? -- Stephen J Smoogen. -- BSD/GNU/Linux How far that little candle throws his beams! So shines a good deed in a naughty world. = Shakespeare. The Merchant of Venice ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] 0.5 State of the Union
Devan Goodwin wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[snip]
On Fedora 10 I see two issues,
spacewalk-setup still hangs at the end restarting services. Everything
seems to be up and running fine including jabberd, I think the problem
is jabberd printing something to stdout/stderr that's messing with the
way we intercept output and log it to rhn-installation.log. If you
switch to another terminal and run service jabberd restart,
spacewalk-setup immediately picks back up and completes. If you trace
this down I believe you land in Setup.pm sub system_debug:
while (PROCESS_OUT) {
print LOGFILE $_;
}
waitpid($pid, 0);
IIRC you never get past the waidpid. It is noteworthy that everything
is up and running at this point, spacewalk-setup just doesn't realize
it.
Jan please look at this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=492194
There's also a lesser problem causing these lines to be printed during
spacewalk-setup:
Use of uninitialized value $uid in chown
at /usr/bin/rhn-generate-pem.pl line 74.
Use of uninitialized value $gid in chown
at /usr/bin/rhn-generate-pem.pl line 74.
This is because we try to change permissions on a file to be owned by
the jabberd user, which doesn't exist at least on F10, it's now just
the jabber user.
I fixed this today: 6ff2e4c035239140e85089bab690ff63add38303
http://tinyurl.com/clqkgn
--
jesus m. rodriguez| jes...@redhat.com
sr. software engineer | irc: zeus
rhn satellite spacewalk | 919.754.4413 (w)
rhce # 805008586930012| 919.623.0080 (c)
+---+
| Those who cannot learn from history |
| are doomed to repeat it. |
| -- George Santayana |
+---+
___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel
