after first update following error happened
Starting name server BIND /usr/sbin/named: error while loading shared libraries: libsasl2.so.2: failed to map segment from shared object: Permission denied
My system is down all ltsp terminals are out as named is needed for ltsp load
HELP! Did you guys test this before making it available… Should have just upgraded but my system is production now thought I was doing right thing!
Dear justlostintime,
I see this is your first post here, thus welcome!
That said, I get the idea that you do not quite understand who we are on these Forums. We are openSUSE users like you. And we are all volunteers in trying to help our fellow users like you. This means that saying " Did you guys test this before making it available" must be send elsewhere. None of us did test, but we did also not make it available.
It might be that some of the people who are making Evergreen available visit the forums, but not as such. They will do so as users (though they may gather valuable information for them in their try to make the Evergreen release possible).
Thus, you are welcome to come here and ask for help (as you did) and people will try to help you. But do not address us as the source of your mishap.
My personal idea is that not very many people here use Evergreen (and I don’t), but let us wait and see if anybody posts here with a valuable answer.
Regards.
On 06/28/2011 11:36 AM, hcvv wrote:
>
> let us wait and see if anybody posts here with a valuable answer.
well, someone else will have to decide if this is valuable or not!
because, i currently have no versions of openSUSE in production service
which have passed their end of life…and, i would not recommend
anyone do so…
nor, have i ever assumed that Evergreen is a good way to have a long
lived dependable, stable, reliable, and secure system…
now, that may come via Evergreen in some future…but, as it is very
much in its project infancy stages and it would be a mistake (in my
opinion) to introduce it to a production machine!! (sand box maybe)
read more here: http://en.opensuse.org/openSUSE:Evergreen and then join
the mail list (linked on that page) for specific questions on who does
the testing and how to undo what you have done to your production system.
of course, undoing will take you back to unsupported and unpatched…
so, if it were me i’d consider using supported software, be that
openSUSE or something else…i’d guess the easiest transition would
probably be to SLES 11, but i never actually used that nor do i know how
smooth a transition that might be (or not)…
oh, sorry i can help with your BIND problem…except to note it seems to
be a “permissions problem” which may or may not be caused by anything
flowing out of Evergreen (my experience is that most “permissions
problems” are self-induced via incorrect administrative procedures)…
justlostintime wrote:
>
> after first update following error happened
>
> Starting name server BIND /usr/sbin/named: error while loading shared
> libraries: libsasl2.so.2: failed to map segment from shared object:
> Permission denied
>
> My system is down all ltsp terminals are out as named is needed for
> ltsp load
>
> HELP! Did you guys test this before making it available… Should
> have just upgraded but my system is production now thought I was doing
> right thing!
>
>
Since this sounds like some kind of bug report, I would suggest you
subscribe to the mailing list for Evergreen. Of course not to drive you away
from here, since there may be other users in the forum who can help you, but
just because I think you will get a more detailed or better and faster reply
by the maintainers of Evergreen than here.
http://lists.rosenauer.org/mailman/listinfo/evergreen
evergreen@lists.rosenauer.org
Hope that helps.
–
PC: oS 11.3 64 bit | Intel Core2 Quad Q8300@2.50GHz | KDE 4.6.4 | GeForce
9600 GT | 4GB Ram
Eee PC 1201n: oS 11.4 64 bit | Intel Atom 330@1.60GHz | KDE 4.6.4 | nVidia
ION | 3GB Ram
Starting name server BIND /usr/sbin/named: error while loading shared libraries: libsasl2.so.2: failed to map segment from shared object: Permission denied
When the error message reports a permission problem, what is the result of:
> ls -l /usr/lib/libsasl*
-rw-r--r-- 1 root root 666 14. Mai 2009 /usr/lib/libsasl2.la
lrwxrwxrwx 1 root root 18 29. Dez 2009 /usr/lib/libsasl2.so -> libsasl2.so.2.0.22
lrwxrwxrwx 1 root root 18 29. Dez 2009 /usr/lib/libsasl2.so.2 -> libsasl2.so.2.0.22
-rwxr-xr-x 1 root root 104844 14. Mai 2009 /usr/lib/libsasl2.so.2.0.22
I have included my results, for you to compare (11.1 with no Evergreen updates). Besides this I can see nothing obvious in the changelog of the new bind package in Evergreen. And libsasl2.so.2 comes from the cyrus-sasl package, which has not been updated in Evergreen.