CFMX 6.1 on RHEL 5 problems

[andrejafah]

We're trying to install CFMX 6.1 (no update) on RedHat Enterprise Linux 5.0 and
get the following when we try to start coldfusion:

[root@rdusn140 bin]# ./coldfusion start
ln: error while loading shared libraries: libc.so.6: cannot open shared object
file: No such file or directory
ps: error while loading shared libraries: libdl.so.2: cannot open shared
object file: No such file or directory
Starting ColdFusion MX...
There may be a few moments before you can access the ColdFusion MX
administrator. This is normal.
sleep: error while loading shared libraries: libc.so.6: cannot open shared
object file: No such file or directory
ps: error while loading shared libraries: libdl.so.2: cannot open shared
object file: No such file or directory
There has been an error starting ColdFusion MX, please check the logs.
[root@rdusn140 bin]#

There's somewhere a hint that some the RHEL 5 kernel is not supported by CFMX
6.1 but that there are workarounds. Unfortunately all I could find is SUSE
related.

Any thoughts?

[Ken Ford - *ACE*]

This is for MX 7.01 but it might help:

[url]http://www.talkingtree.com/blog/index.cfm/2005/10/13/OCFMG20051013[/url]

--
Ken Ford
Adobe Community Expert
Fordwebs, LLC
[url]http://www.fordwebs.com[/url]


"andrejafah" <webforumsuser@macromedia.com> wrote in message news:etp9hd$g0r$1@forums.macromedia.com...

> We're trying to install CFMX 6.1 (no update) on RedHat Enterprise Linux 5.0 and
> get the following when we try to start coldfusion:
>
> [root@rdusn140 bin]# ./coldfusion start
> ln: error while loading shared libraries: libc.so.6: cannot open shared object
> file: No such file or directory
> ps: error while loading shared libraries: libdl.so.2: cannot open shared
> object file: No such file or directory
> Starting ColdFusion MX...
> There may be a few moments before you can access the ColdFusion MX
> administrator. This is normal.
> sleep: error while loading shared libraries: libc.so.6: cannot open shared
> object file: No such file or directory
> ps: error while loading shared libraries: libdl.so.2: cannot open shared
> object file: No such file or directory
> There has been an error starting ColdFusion MX, please check the logs.
> [root@rdusn140 bin]#
>
> There's somewhere a hint that some the RHEL 5 kernel is not supported by CFMX
> 6.1 but that there are workarounds. Unfortunately all I could find is SUSE
> related.
>
> Any thoughts?
>

[speedpedal]

First of all, RHEL5 is a new release. It's not even supported and QA'd in CFMX
7. So officially, RHEL5 is not supported in CFMX 6.1.

Having said that, the error your are having is similar to the one discussed by
one of our colleague in his blog. Check out this post:


[url]http://www.talkingtree.com/blog/index.cfm/2006/12/6/Running-ColdFusion-MX-7-on-F[/url]
edora-Core-6-Linux

Hope this helps.

[andrejafah]

A quick question - is RHEL 4.0 certified for CF 6.1? If yes, up to which Update?

Thanks.

[Ken Ford - *ACE*]

Doesn't say which update:

[url]http://www.adobe.com/products/coldfusion/productinfo/systemreqs/[/url]

--
Ken Ford
Adobe Community Expert
Fordwebs, LLC
[url]http://www.fordwebs.com[/url]


"andrejafah" <webforumsuser@macromedia.com> wrote in message news:etui5o$b60$1@forums.macromedia.com...

>A quick question - is RHEL 4.0 certified for CF 6.1? If yes, up to which Update?
>
> Thanks.

[Ken Ford - *ACE*]

Oops you said 6.1 - sorry:

Doesn't look like it:

[url]http://www.adobe.com/products/coldfusionmx61/productinfo/systemreqs/[/url]

--
Ken Ford
Adobe Community Expert
Fordwebs, LLC
[url]http://www.fordwebs.com[/url]


"Ken Ford - *ACE*" <newsgroups@fordwebs.com> wrote in message news:etun0o$h8k$1@forums.macromedia.com...

> Doesn't say which update:
>
> [url]http://www.adobe.com/products/coldfusion/productinfo/systemreqs/[/url]
>
> --
> Ken Ford
> Adobe Community Expert
> Fordwebs, LLC
> [url]http://www.fordwebs.com[/url]
>
>
> "andrejafah" <webforumsuser@macromedia.com> wrote in message news:etui5o$b60$1@forums.macromedia.com...

>>A quick question - is RHEL 4.0 certified for CF 6.1? If yes, up to which Update?
>>
>> Thanks.