Koozali.org: home of the SME Server

Obsolete Releases => SME Server 7.x => Topic started by: Kryptex on April 20, 2012, 12:09:36 PM

Title: smeserver logonscript
Post by: Kryptex on April 20, 2012, 12:09:36 PM
Hey all,

I'm having trouble with installing the smeserver-tw-logonscript.

After using the command "yum --enablerepo=smecontribs install smeserver-tw-logonscript"
I get the following error:

Cannot find a valid baseurl for repo:base

I've also tried this command that was in the sticky and then attempted to install it again, but it still didn't work.

yum --disablerepo=base --disablerepo=updates update

Anyone got any suggestions?
Title: Re: smeserver logonscript
Post by: Kryptex on April 20, 2012, 12:25:07 PM
Heres a screenshot, and im running SME 7.5 btw

http://tinypic.com/r/2rp4qxv/5
Title: Re: smeserver logonscript
Post by: mmccarn on April 20, 2012, 01:42:26 PM
Have you updated your yum within the last few weeks as described here?
http://forums.contribs.org/index.php/topic,48424.msg240692.html#msg240692

Title: Re: smeserver logonscript
Post by: Kryptex on April 20, 2012, 06:25:54 PM
Hi,

After using "yum --disablerepo=base --disablerepo=updates update"

I re-ran the server configuration and rebooted it, now the logonscript part seems to be added to the server manager!:)

However, in the server manager it still says I have to re-run my configuration and reboot the server, but I already did that. Anyone know how I can get rid of that message or fix it properly?
Title: Re: smeserver logonscript
Post by: chris burnat on April 21, 2012, 12:58:05 AM
After using "yum --disablerepo=base --disablerepo=updates update"
I re-ran the server configuration and rebooted it, now the logonscript part seems to be added to the server manager!:)


Please note comment #3 by mmccan below, pointing to comment #5 in the sticky have you followed this suggestion?  If you have followed this advice fully and still experience an issue, your problem may be the result of some error on your part - or a bug.  You should then open a bug report at Bugzilla. 


Quote
However, in the server manager it still says I have to re-run my configuration and reboot the server, but I already did that. Anyone know how I can get rid of that message or fix it properly?

Have you executed the command:
Code: [Select]
signal-event post-upgrade; signal-event reboot

Note: you have to wait for the command to be fully executed before closing your terminal, or the reconfiguration may fail.  If in doubt, do it again, there is no harm done duplicating a reconfiguration.  When all done (it takes a while) and after reboot of your server, check the logs (messages) to ensure that all is well.

Title: Re: smeserver logonscript
Post by: Kryptex on April 27, 2012, 10:18:08 AM
Please note comment #3 by mmccan below, pointing to comment #5 in the sticky have you followed this suggestion?  If you have followed this advice fully and still experience an issue, your problem may be the result of some error on your part - or a bug.  You should then open a bug report at Bugzilla. 


Have you executed the command:
Code: [Select]
signal-event post-upgrade; signal-event reboot

Note: you have to wait for the command to be fully executed before closing your terminal, or the reconfiguration may fail.  If in doubt, do it again, there is no harm done duplicating a reconfiguration.  When all done (it takes a while) and after reboot of your server, check the logs (messages) to ensure that all is well.

I tried but it says signal-event command not found?
Title: Re: smeserver logonscript
Post by: janet on April 27, 2012, 11:06:06 AM
Kryptex

Try this
/sbin/e-smith/signal-event post-upgrade
/sbin/e-smith/signal-event reboot

Are you doing this as the root user ?
If not and you have setup another (command prompt) user, then perhaps the path is not setup correctly for that user.
Title: Re: smeserver logonscript
Post by: Kryptex on April 29, 2012, 10:52:55 AM
Kryptex

Try this
/sbin/e-smith/signal-event post-upgrade
/sbin/e-smith/signal-event reboot

Are you doing this as the root user ?
If not and you have setup another (command prompt) user, then perhaps the path is not setup correctly for that user.

That worked, cheers.

Was logged in as root, yes.