Topic: SME Crontab Problems after SME Server Update May 6, 2008

[pmstewart]

I searched bugzilla for authorized contribs and sme-crontab_manager is not one of them. (sme-crontab_manager-1.2-4.noarch.rpm installed)

Currently testing 3 servers with SME 7.3 one which has no updates. The contrib works fine on this server.

When updates are complete there is a line which appears at boot and in the logs - and if the contrib is uninstalled and reinstalled the same message comes
up after installation in the terminal window. The server manager panel does not display correctly until the contrib has been uninstalled.

Code: [Select]

not well-formed (invalid token) at line 14, column 59, byte 369 at /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi/XML/Parser.pm line 187

smeserver trap post-install: sme-crontab_manager

Currently testing crontab manager for ddns functionality

Will be glad to post in bug tracker - this is to make others aware updating could cause this problem if the contrib is installed.

[cactus]

Code: [Select]

not well-formed (invalid token) at line 14, column 59, byte 369 at /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi/XML/Parser.pm line 187

smeserver trap post-install: sme-crontab_manager

Currently testing crontab manager for ddns functionality

Will be glad to post in bug tracker - this is to make others aware updating could cause this problem if the contrib is installed.

This is most likely due to the mentined contrib not having UTF8 locale encoding: http://bugs.contribs.org/show_bug.cgi?id=4135

And should not really be any problem at all.

[pmstewart]

Well, if your idea of a good time means having more than half of your server-manager entries listed under the heading of "unknown" life is grand.

And since this was the first item found with unhappy results the contrib was removed before any further testing could take place.

Maybe this could very well be user error since the contrib was installed with

Code: [Select]


yum localinstall sme-crontab_manager


instead of the suggested method from the how-to

Code: [Select]


rpm -e sme-crontab_manager


Any thoughs?

[cactus]

Well, if your idea of a good time means having more than half of your server-manager entries listed under the heading of "unknown" life is grand.

And since this was the first item found with unhappy results the contrib was removed before any further testing could take place.

Maybe this could very well be user error since the contrib was installed with

Code: [Select]


yum localinstall sme-crontab_manager


instead of the suggested method from the how-to

Code: [Select]


rpm -e sme-crontab_manager


Any thoughs?

I think you are misunderstanding things here, the first is for installation of a RPM on your file system, the second is the command to remove a installed RPM.

Installation from a repository using yum install and from a the file system using yum localinstall should not make any difference in any other aspect than the RPM being available after download or directly on the FS.

[cactus]

Any thoughs?

Did you also try to update your contribs against the SME Contribs repository using:

Code: [Select]

yum update --enablerepo=smecontribs

[mercyh]

Method of install will not make any difference.

sme-crontab_manager is listed here http://wiki.contribs.org/Translations#Outdated_contribs
as not updated to the UTF8 translation format. Until it is updated you will either have to do without it or use it with the unsorted server-manager menu.

The contribs are functional but the menu is ugly.

EDIT: Cactus I am getting slower all the time. You got TWO posts in while I was writing this one. 

[cactus]

EDIT: Cactus I am getting slower all the time. You got TWO posts in while I was writing this one. 

Don't bother... I am a rapid typer.

[mercyh]

And I am a slow THINKER

[cactus]

And I am a slow THINKER

LOL

[pmstewart]

Both you guys are a hoot!....LOL

I apologize - copied the wrong code to put in the post.....
I should have put the rpm install command in instead of the rpm remove - oops!

Since I saw a current how-to in the wiki for crontab I didn't even think to look at the list
of outdated contribs.......twice oops!

However, have not tried the

Code: [Select]


yum update --enablerepo=smecontribs


Will give it a go and report back.....thanks gents!

[pmstewart]

By running the yum update enabling the repo contribs brings a step in the right direction - for at least one server

Now the crontab manager is the only thing showing as "unknown" in the server manager on server 1 which has now received it's updates.

Server 2 which had updates installed is not effected by updating or through removal and reinstall

Big ARGH!

[cactus]

By running the yum update enabling the repo contribs brings a step in the right direction - for at least one server

Now the crontab manager is the only thing showing as "unknown" in the server manager on server 1 which has now received it's updates.

Server 2 which had updates installed is not effected by updating or through removal and reinstall

Big ARGH!

Than you most likely have some other nog UTF8 enabled contribs installed. Look at the Translation page in the wiki, there are some clues there. A search in the forums would have also brought you a lot of information as since April 19th, the day of the release, a lot has been written about the update here.

[pmstewart]

Cactus,

U R Awsome!

Thank you and yes I have seen some of the posts reference the April 19th update.

Just haven't spent enough time searching and reading.......

[yythoss]

I have make a script that change the language files to UTF-8.
The script don't touch files, they are allways in UTF-8 and you don't must uninstall your contribs.

Look at this Thread:

http://forums.contribs.org/index.php?topic=40771.0

yythoss

[e[nt]e]

Look at this Thread:

http://forums.contribs.org/index.php?topic=40771.0

I think most of the people reading this don't understand German. So here is a short English How-To in the wiki:
http://wiki.contribs.org/Translations#Conversion_script