Topic: Unknown entries after update

[key]

Hello everybody,

after the updates today I have two new entries in Server-Manager under "Unknown".

Does one has the same and knows where are they coming from?

Thx,
key

[networks]

Hello,

I have the same, but for me it's four new entries in Server-Manager under "Unknown"
Also after the last updates

Unknown
921c47fb4be0fedd916a0cce181cd741
3095103c03a5b0f529e7e33001aa2896
aee8dfcb0a38912ab299637145b6c436
721351716a1dc1c78449143a034b50fe

What's this ?
How to remove it ?

[key]

I have:

76f355e6646aebb2ed596d4e02a7fd28
1fe90ab41b6416c3712d5c12840d3ec7

Can someone help?

key

[networks]

For me this happen after these yum updates :

Nov 25 19:41:52 Updated: perl-IO-Compress-Base.noarch 2.008-1.el4.rf
Nov 25 19:41:53 Updated: perl-Compress-Raw-Zlib.i386 2.008-1.el4.rf
Nov 25 19:41:53 Updated: perl-IO-Compress-Zlib.noarch 2.008-1.el4.rf
Nov 25 19:41:53 Updated: perl-CGI-Persistent.noarch 1.00-1.el4.rf
Nov 25 19:41:53 Updated: perl-Error.noarch 0.17010-1.el4.rf
Nov 25 19:41:53 Updated: perl-Text-Iconv.i386 1.7-1.el4.rf
Nov 25 19:41:53 Updated: perl-Mail-DKIM.noarch 0.29-1.el4.rf
Nov 25 19:41:54 Updated: perl-DBI.i386 1.601-1.el4.rf
Nov 25 19:41:54 Updated: htop.i386 0.7-1.el4.rf
Nov 25 19:41:54 Updated: perl-Compress-Zlib.noarch 2.008-1.el4.rf
Nov 25 19:41:54 Updated: perl-HTML-Tabulate.noarch 0.26-1.el4.rf
Nov 25 19:41:54 Updated: perl-IO-Zlib.noarch 1.08-1.el4.rf
Nov 25 19:41:54 Updated: perl-Quota.i386 1.6.0-1.el4.rf
Nov 25 19:41:54 Updated: perl-Crypt-Cracklib.i386 1.1-1.el4.rf
Nov 25 19:41:54 Updated: perl-I18N-AcceptLanguage.noarch 1.04-1.el4.rf
Nov 25 19:41:54 Updated: perl-CGI-FormMagick.noarch 0.92-13.el4.sme

Thanks for your help,
Networks

[key]

I don't know which I had.

But, it was after the update today, didn't had that before.

key

[networks]

I think the problem is with the new version of FormMagick
But how to fix ?

[jncs]

This also happens to me!

It start after happen after these yum updates:

==============================================================
WARNING: Additional commands may be required after running yum
==============================================================
Loading "fastestmirror" plugin
Loading "smeserver" plugin
Setting up repositories
Loading mirror speeds from cached hostfile
Reading repository metadata in from local files
Excluding Packages from CentOS - updates
Finished
Excluding Packages from CentOS - os
Finished
Recently Added Packages
htop.i386                                0.7-1.el4.rf           smeupdates     
perl-CGI-FormMagick.noarch               0.92-13.el4.sme        smeupdates     
perl-CGI-Persistent.noarch               1.00-1.el4.rf          smeupdates     
perl-Class-ParamParser.noarch            1.041-1.el4.rf         smeos           
perl-Crypt-Cracklib.i386                 1.1-1.el4.rf           smeupdates     
perl-DBI.i386                            1.601-1.el4.rf         smeupdates     
perl-Error.noarch                        0.17010-1.el4.rf       smeupdates     
perl-HTML-Tabulate.noarch                0.26-1.el4.rf          smeupdates     
perl-I18N-AcceptLanguage.noarch          1.04-1.el4.rf          smeupdates     
perl-IO-Zlib.noarch                      1.08-1.el4.rf          smeupdates     
perl-Object-Persistence.noarch           0.92-1.el4.rf          smeos           
perl-Quota.i386                          1.6.0-1.el4.rf         smeupdates     
perl-Text-Iconv.i386                     1.7-1.el4.rf           smeupdates     
perl-Time-TAI64.noarch                   2.11-1.el4.rf          smeos           
================================================================
No new rpms were installed. No additional commands are required.
================================================================

It seems to me that this error has to be with some perl update. Which one?

The number of entries in the Unknown section is the number of times we access to the others sections in server-manager. If we access tree times to log files (for example) there will be tree random named files in the unknown section.

This files can be deleted in folder (directory): /etc/e-smith/web/panels/manager/cgi-bin
but deleting the files will not resolve the problem! 

When we access the server-manager for the next time it will be happening again!

[panda]

I've got the same.
I've also reported it to the bug tracker as #3586

Chris.

[CharlieBrady]

I've also reported it to the bug tracker as #3586

Thanks. If the others had reported via the bug tracker rather than talking amongst themselves here in the forum, someone would have started working on a solution sooner.

Please don't gossip in the forums - report any malfunction via the bug tracker.

Thanks.

[jncs]

I just want to thanks to all the people of SME Server bug team for the quickly resolution of this problem!

I must agree with CharlieBrady and present to all my apologies! This issue should be reported immediately in the bug tracker! Like the Chris Dallimore (panda) has done! (Thanks Chris!)

To all that just arrived here after that, the problem was solved by perl-CGI-FormMagick.noarch 0.92-14.el4.sme update.

You can get all the solution in http://bugs.contribs.org/show_bug.cgi?id=3586.

Just a think: When and how do we know if some problem we found it is really a bug or just a some kind of configuration issue?!? People who post here sometimes don't know if that problem happens just to them or if it happens to other... Should we report some kind of issue if that just happens in our SME Server?

[panda]

I just want to thanks to all the people of SME Server bug team for the quickly resolution of this problem!

Likewise. Problem confirmed, identified and resolved in double-quick time. Impressive!

Just a think: When and how do we know if some problem we found it is really a bug or just a some kind of configuration issue?!? People who post here sometimes don't know if that problem happens just to them or if it happens to other... Should we report some kind of issue if that just happens in our SME Server?

My thoughts:
If a bug is suspected, report it on the bug tracker. I don't think the dev team should have to trawl the discussions to identify any possible problems. They work hard in giving us this excellent package, so I think the least we can do is deliver to them (via the bug tracker) any potential issues. If the report turns out to be bogus, it can soon be closed, but at least the dev team are aware and can confirm or rule out if the problem is with SME.

I'd rather Charlie chastise me for reporting a dud bug, than not reporting a real one...

Chris.

[byte]

I just want to thanks to all the people of SME Server bug team [..]

Shouldn't take to long to thank all the people as there are not that many Don't forget any help is needed not just in the wiki but in the Bugs as well

Just a think: When and how do we know if some problem we found it is really a bug or just a some kind of configuration issue?!? People who post here sometimes don't know if that problem happens just to them or if it happens to other... Should we report some kind of issue if that just happens in our SME Server?

Basically if SME Server doesn't work "out of the box" then you maybe seeing a bug, of course if people read the documentation properly a configuration issue may not be the problem, if it is a configuration issue and not a bug will would just mark the bug invalid and point to our forums for support.

[jncs]

Shouldn't take to long to thank all the people as there are not that many Don't forget any help is needed not just in the wiki but in the Bugs as well

byte:

How can I help this great project? How can I help the Bugs team? Which knowledge is necessary to participate in the team?

[byte]

How can I help this great project? How can I help the Bugs team? Which knowledge is necessary to participate in the team?

Get a bug account (unless you already have one) familiarize yourself with the bug layout which may look scary at first but trust me its not that difficult to get to grips with (hell i did )  make sure you keep an eye on all bugs for example log in to your account and "Email preferences" and click "enable all mail" that way you won't miss a trick!

You could start by using a test machine and loading up:

http://distro.ibiblio.org/pub/linux/distributions/smeserver/releases/7/smetest/i386/repodata/repoview/e-smith-backup-0-1.15.0-7.el4.sme.html

Play around and try break that package with different settings. Think you could help out over there ?

[kruhm]

"How can I help this great project? How can I help the Bugs team? Which knowledge is necessary to participate in the team?"

http://wiki.contribs.org/How_you_can_help

[byte]

jncs or (anyone else) are you still up to helping out over at bugs we need some verifications done


http://bugs.contribs.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=SME+Server+Release+7.X&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=RESOLVED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&negate0=1&field0-0-0=resolution&type0-0-0=substring&value0-0-0=INVA&field0-0-1=resolution&type0-0-1=substring&value0-0-1=DUPL&field1-0-0=bug_status&type1-0-0=regexp&value1-0-0=CLOSED%7CVERIFIED%7CRESOLVED&field1-1-0=resolution&type1-1-0=regexp&value1-1-0=FIX