|
List Info
Thread: Unabel to open Horde web client
|
|
| Unabel to open Horde web client |

|
2007-04-03 05:34:04 |
|
Dear friends
I have installed Kolab+horde on centOs like this
wget -q -r -11 -nd --no-parent httpd://max.kde.org:8080/mirrors/ftp/kolab.org/server/beta/kolab-server-2.1-rc-1/sources/
rm obmtool.conf
wget -q -r -l1 -nd --no-parent http://build.pardus.de/downloads/kolab-horde-tmp
sh obmtool kolab
It's loaded successfully but i am not able to open horde web
tool, But i can open kolab admin
(https://host.domain.com/admin)
But I am not able to open Horde http://host.domain.com/horde web page for configuration
plz do the help
thnx
rajnish
|
| Re: Unabel to open Horde web client |

|
2007-04-03 05:36:12 |
|
On 4/3/07, rajnish kumar < kumarrajnishgupta gmail.com">kumarrajnishgupta gmail.com> wrote:
Dear friends
I have installed Kolab+horde on centOs like this
wget -q -r -11 -nd --no-parent httpd://max.kde.org:8080/mirrors/ftp/kolab.org/server/beta/kolab-server-2.1-rc-1/sources/
rm obmtool.conf
wget -q -r -l1 -nd --no-parent http://build.pardus.de/downloads/kolab-horde-tmp
sh obmtool kolab
It's loaded successfully but i am not able to open horde web
tool, But i can open kolab admin
(https://host.domain.com/admin)
But I am not able to open Horde http://host.domain.com/horde web page for configuration
plz do the help
thnx
rajnish
|
| Re: Unabel to open Horde web client |
  Germany |
2007-04-03 06:35:05 |
Hi Rajnish,
"rajnish krishna" <krishnarajnishgupta gmail.com> writes:
> I have installed Kolab+horde on
centOs like this
>
> wget -q -r -11 -nd --no-parent
httpd://max.kde.org:8080/mirrors/ftp/kolab.org/server/beta/k
olab-server-2.1-rc-1/sources/
>
> rm obmtool.conf
>
> wget -q -r -l1 -nd --no-parent http
://build.pardus.de/downloads/kolab-horde-tmp
>
> sh obmtool kolab
Did you get any errors when you ran this command?
> It's loaded successfully but i am not able to open
horde web tool,
> But i can open kolab admin (https://host.domain.com
/admin) But I am
> not able to open Horde http://host.domain.com/h
orde web page for
> configuration
Does the only troubleshooting hint I entered so far
(http://wiki.kolab.org/index.php/Kolab2_Serv
er_Troubleshooting_-_Horde)
help you with diagnosing the problem?
Cheers,
Gunnar
--
____ http://www.pardus.de
_________________ http://gunnarwrobel.de _
>> Mail at ease - Rent a kolab groupware server at
p rdus <<
p rdus Kolab work is funded in part by KDAB and the
Kolab Konsortium
_______________________________________________
Kolab-users mailing list
Kolab-users kolab.org
https:
//kolab.org/mailman/listinfo/kolab-users
|
|
| Re: Unabel to open Horde web client |

|
2007-04-03 07:40:18 |
|
Dear sir
thnx
for for reply i know you are only the person who can send reply about
kolab+horde
At the time of installation some warning has come which have been
posted here, but the text which are in the bold/itaic and red color is
the last log. But I am not getting any conclusion like that how many
rpm installed like this
with regds
rajnish
Warning: Error, PHP5 token encountered in Yaml/Yaml.php, analysis should be in PHP5
Warning: Error, PHP5 token encountered in Yaml/Yaml.php, analysis should be in PHP5
Warning: Error, PHP5 token encountered in Yaml/Yaml.php, analysis should be in PHP5
Warning: Error, PHP5 token encountered in Yaml/Yaml.php, analysis should be in PHP5
Warning: Error, PHP5 token encountered in Yaml/Yaml.php, analysis should be in PHP5
Warning: Error, PHP5 token encountered in Yaml/Yaml/Node.php, analysis should be in PHP5
Warning: Error, PHP5 token encountered in Yaml/Yaml/Node.php, analysis should be in PHP5
Warning: Error, PHP5 token encountered in Yaml/Yaml/Node.php, analysis should be in PHP5
Warning: Error, PHP5 token encountered in Yaml/Yaml/Node.php, analysis
should be in PHP5 Warning: Error, PHP5 token encountered in
Yaml/Yaml/Node.php, analysis should be in PHP5 Warning: Error, PHP5
token encountered in Yaml/Yaml/Node.php, analysis should be in PHP5
Warning: Error, PHP5 token encountered in Yaml/Yaml/Loader.php, analysis should be in PHP5
Warning: Error, PHP5 token encountered in Yaml/Yaml/Loader.php, analysis should be in PHP5
Warning: Error, PHP5 token encountered in Yaml/Yaml/Loader.php, analysis should be in PHP5
Warning: Error, PHP5 token encountered in Yaml/Yaml/Loader.php, analysis should be in PHP5
Warning: Error, PHP5 token encountered in Yaml/Yaml/Loader.php,
analysis should be in PHP5 Warning: Error, PHP5 token encountered in
Yaml/Yaml/Loader.php, analysis should be in PHP5
Warning: Error, PHP5 token encountered in Yaml/Yaml/Loader.php,
analysis should be in PHP5 Warning: Error, PHP5 token encountered in
Yaml/Yaml/Loader.php, analysis should be in PHP5
Warning: Error, PHP5 token encountered in Yaml/Yaml/Loader.php, analysis should be in PHP5
Warning: Error, PHP5 token encountered in Yaml/Yaml/Loader.php, analysis should be in PHP5
Warning: Error, PHP5 token encountered in Yaml/Yaml/Loader.php,
analysis should be in PHP5 Warning: Error, PHP5 token encountered in
Yaml/Yaml/Loader.php, analysis should be in PHP5 Warning: Error, PHP5
token encountered in Yaml/Yaml/Loader.php, analysis should be in PHP5
Warning: Error, PHP5 token encountered in Yaml/Yaml/Loader.php, analysis should be in PHP5
Warning: Error, PHP5 token encountered in Yaml/Yaml/Loader.php, analysis should be in PHP5
Warning: Error, PHP5 token encountered in Yaml/Yaml/Loader.php, analysis should be in PHP5
Warning: Error, PHP5 token encountered in Yaml/Yaml/Loader.php,
analysis should be in PHP5 Warning: Error, PHP5 token encountered in
Yaml/Yaml/Loader.php, analysis should be in PHP5
Warning: Error, PHP5 token encountered in Yaml/Yaml/Loader.php, analysis should be in PHP5
Warning: Error, PHP5 token encountered in Yaml/Yaml/Loader.php,
analysis should be in PHP5 Warning: Error, PHP5 token encountered in
Yaml/Yaml/Loader.php, analysis should be in PHP5
Warning: Error, PHP5 token encountered in Yaml/Yaml/Loader.php,
analysis should be in PHP5 Warning: Error, PHP5 token encountered in
Yaml/Yaml/Loader.php, analysis should be in PHP5
Warning: Error, PHP5 token encountered in Yaml/Yaml/Dumper.php, analysis should be in PHP5
Warning: Error, PHP5 token encountered in Yaml/Yaml/Dumper.php, analysis should be in PHP5
Warning: Error, PHP5 token encountered in Yaml/Yaml/Dumper.php, analysis should be in PHP5
|This
OpenPKG package is of class
JUNK.
|
| It is in development state and still not even ready for evaluation. |
| Do not use it at all, as it is definitely unstable and incomplete. |
|
Only CORE and BASE class packages are production
grade.
|
+-----------------------------------------------------------------------------+
+ cd /kolab/RPM/TMP
+ rm -rf horde-turba-kolab-20070131
+ /kolab/lib/openpkg/shtool mkdir -f -p -m 755 horde-turba-kolab-20070131
+ cd horde-turba-kolab-20070131
+ /kolab/lib/openpkg/gzip -dc /kolab/RPM/SRC/horde-turba-kolab/horde-turba-kolab-20070131.tar.gz
+ /kolab/lib/openpkg/tar -xf -
+ STATUS=0
+ '['; 0 -ne 0 ']';
+ exit 0
Executing(%build): env -i /kolab/lib/openpkg/bash --norc --noprofile --posix -e /kolab/RPM/TMP/rpm-tmp.30142
+ cd /kolab/RPM/TMP
+ cd horde-turba-kolab-20070131
+ exit 0
Executing(%install): env -i /kolab/lib/openpkg/bash --norc --noprofile --posix -e /kolab/RPM/TMP/rpm-tmp.30142
+ cd /kolab/RPM/TMP
+ cd horde-turba-kolab-20070131
+ rm -rf /kolab/RPM/TMP/horde-turba-kolab-20070131-root
+ /kolab/lib/openpkg/shtool install -d /kolab/RPM/TMP/horde-turba-kolab-20070131-root/kolab/var/kolab/www/horde/turba
+ /kolab/lib/openpkg/shtool install -d /kolab/RPM/TMP/horde-turba-kolab-20070131-root/kolab/etc/kolab/templates
+ cd turba/config
+ for fl in '*.dist'
+ cp attributes.php.dist attributes.php
+ for fl in '*.dist'
+ cp menu.php.dist menu.php
+ for fl in '*.dist'
+ cp mime_drivers.php.dist mime_drivers.php
+ for fl in '*.dist'
+ cp prefs.php.dist prefs.php
+ for fl in '*.dist'
+ cp sources.php.dist sources.php
+ cd ../..
+ cp -r turba /kolab/RPM/TMP/horde-turba-kolab-20070131-root/kolab/var/kolab/www/horde/
+
/kolab/lib/openpkg/shtool install -c -m 644 -e 's; l_susr ;root;g9; -e
's; l_sgrp ;root;g9; -e 's; l_suid ;0;g' -e 's; l_sgid ;0;g' -e
's; l_musr ;kolab;g39; -e 's; l_mgrp ;kolab;g39; -e 's; l_muid ;19414;g39; -e
's; l_mgid ;19414;g39; -e 's; l_rusr ;kolab-r;g' -e
's; l_rgrp ;kolab-r;g' -e 's; l_ruid ;19415;g39; -e 's; l_rgid ;19415;g39;
-e 's; l_nusr ;kolab-n;g' -e 's; l_ngrp ;kolab-n;g' -e
's; l_nuid ;19416;g39; -e 's; l_ngid ;19416;g39; -e 's; l_prefix ;/kolab;g'
-e 's; l_prefix_static ;/kolab;g'
/kolab/RPM/SRC/horde-turba-kolab/conf.php
/kolab/RPM/SRC/horde-turba-kolab/sources.php
/kolab/RPM/TMP/horde-turba-kolab-20070131-root/kolab/var/kolab/www/horde/turba/config/
+
/kolab/lib/openpkg/rpmtool files -v -ofiles
-r/kolab/RPM/TMP/horde-turba-kolab-20070131-root
'%defattr(-,kolab,kolab)' /kolab '%not %dir
{/kolab,/kolab/*,/kolab/etc/rc.d,/kolab/man/*}39; '%config(noreplace)
/kolab/var/kolab/www/horde/turba/config/conf.php9; '%config(noreplace)
/kolab/var/kolab/www/horde/turba/config/sources.php'
rpmtool:files: pass 1 (preparation and syntactical expansions)
rpmtool:files: pass 2 (filesystem-based expansions)
rpmtool:files: pass 3 (duplication removal and cleanup)
+ exit 0
Processing files: horde-turba-kolab-20070131-1
Wrote: /kolab/RPM/PKG/horde-turba-kolab-20070131-1.ix86-rhl4.4-kolab.rpm
Executing(%clean): env -i /kolab/lib/openpkg/bash --norc --noprofile --posix -e /kolab/RPM/TMP/rpm-tmp.9483
+ cd /kolab/RPM/TMP
+ cd horde-turba-kolab-20070131
+ rm -rf /kolab/RPM/TMP/horde-turba-kolab-20070131-root
+ exit 0
Executing(--clean): env -i /kolab/lib/openpkg/bash --norc --noprofile --posix -e /kolab/RPM/TMP/rpm-tmp.9483
+ cd /kolab/RPM/TMP
+ rm -rf horde-turba-kolab-20070131
+ exit 0
Preparing...
##################################################
horde-turba-kolab ##################################################
On 4/3/07, Gunnar Wrobel < wrobel pardus.de" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">wrobel pardus.de
> wrote:
Hi Rajnish,
"rajnish kumar" < kumarrajnishgupta gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">kumarrajnishgupta gmail.com> writes:
>
I have installed Kolab+horde on centOs like this > > wget -q -r -11 -nd --no-parent httpd://max.kde.org:8080/mirrors/ftp/kolab.org/server/beta/kolab-server-2.1-rc-1/sources/ > > rm obmtool.conf
> > wget -q -r -l1 -nd --no-parent http://build.pardus.de/downloads/kolab-horde-tmp
> > sh obmtool kolab
Did you get any errors when you ran this command?
> It's loaded successfully but i am not able to open horde web tool, > But i can open kolab admin (
https://host.domain.com/admin) But I am > not able to open Horde
http://host.domain.com/horde web page for > configuration
Does the only troubleshooting hint I entered so far
(
http://wiki.kolab.org/index.php/Kolab2_Server_Troubleshooting_-_Horde) help you with diagnosing the problem?
Cheers,
Gunnar
-- ____
http://www.pardus.de _________________
http://gunnarwrobel.de _
>> Mail at ease - Rent a kolab groupware server at p rdus <<
p rdus Kolab work is funded in part by KDAB and the Kolab Konsortium
|
| Re: Unabel to open Horde web client |
  Germany |
2007-04-03 07:45:14 |
Hi Rajnish,
"rajnish krishna" <krishnarajnishgupta gmail.com> writes:
> Preparing...
##################################################
> horde-turba-kolab
##################################################
sorry, but the log you provided only displays that the
installation of
horde-turba was successful. It did not show anything
unusual.
I believe that the build log for the horde-kolab package
would be more
critical. Can you send the corresponding part?
Cheers,
Gunnar
--
____ http://www.pardus.de
_________________ http://gunnarwrobel.de _
>> Mail at ease - Rent a kolab groupware server at
p rdus <<
p rdus Kolab work is funded in part by KDAB and the
Kolab Konsortium
_______________________________________________
Kolab-users mailing list
Kolab-users kolab.org
https:
//kolab.org/mailman/listinfo/kolab-users
|
|
| Re: Unabel to open Horde web client |

|
2007-04-03 08:03:22 |
|
Dear sir
I think this log will help you to get resolve my problem
thnx with regds
rajnish
RPM build errors:
Bad exit status from /kolab/RPM/TMP/rpm-tmp.44967 (%install)
obmtool:WARNING: install failure. Missing /kolab/RPM/PKG/horde-kolab-20070319-2.ix86-rhl4.4-kolab.rpm
install horde-imp-kolab-20070213-1
rebuild horde-imp-kolab-20070213-1
Installing /kolab/RPM/PKG/horde-imp-kolab-20070213-1.src.rpm
Executing(%prep): env -i /kolab/lib/openpkg/bash --norc --noprofile --posix -e /kolab/RPM/TMP/rpm-tmp.59460
+ cd /kolab/RPM/TMP
+ set +x
On 4/3/07, Gunnar Wrobel < wrobel pardus.de" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">wrobel pardus.de
> wrote:
Hi Rajnish,
"rajnish kumar" < kumarrajnishgupta gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">kumarrajnishgupta gmail.com> writes: >
Preparing... ################################################## >
horde-turba-kolab
##################################################
sorry, but the log you provided only displays that the installation of horde-turba was successful. It did not show anything unusual.
I believe that the build log for the horde-kolab package would be more
critical. Can you send the corresponding part?
Cheers,
Gunnar
-- ____ http://www.pardus.de
_________________ http://gunnarwrobel.de
_
>> Mail at ease - Rent a kolab groupware server at p rdus <<
p rdus Kolab work is funded in part by KDAB and the Kolab Konsortium
|
| Re: Unabel to open Horde web client |
  Germany |
2007-04-03 08:15:16 |
Hi Rajnish,
> I think this log will help you to get
resolve my problem
well, nearly ;)
>
> RPM build errors:
> Bad exit status from /kolab/RPM/TMP/rpm-tmp.44967
(%install)
> obmtool:WARNING: install failure. Missing
/kolab/RPM/PKG/horde-kolab-20070319-2.ix86-rhl4.4-kolab.rpm
This tells me that there was indeed a build error affecting
horde-kolab (Bad exit status). It does not tell me what
actually
happened there. This would have been in the lines right
above that
message So could
send the lines above the line that says "RPM build
errors"?
Did you also check
http://wiki.kolab.org/index.php/Kolab2_Serv
er_Troubleshooting_-_Horde
and followed the instructions given there?
Running
rm -rf /kolab/RPM/PKG/*
rm -rf /kolab/RPM/TMP/*
rm -rf /kolab/RPM/SRC/*
would clean your build environment. Afterwards you could try
to run
sh obmtool kolab
again. Did you do that?
Cheers,
Gunnar
--
____ http://www.pardus.de
_________________ http://gunnarwrobel.de _
>> Mail at ease - Rent a kolab groupware server at
p rdus <<
p rdus Kolab work is funded in part by KDAB and the
Kolab Konsortium
_______________________________________________
Kolab-users mailing list
Kolab-users kolab.org
https:
//kolab.org/mailman/listinfo/kolab-users
|
|
| Re: Unabel to open Horde web client |

|
2007-04-03 08:29:26 |
|
Dear sir
Plz find upper line as you required
with regds
rajnish
install horde-kolab-20070319-2
rebuild horde-kolab-20070319-2
Installing /kolab/RPM/PKG/horde-kolab-20070319-2.src.rpm
Executing(%prep): env -i /kolab/lib/openpkg/bash --norc --noprofile --posix -e /kolab/RPM/TMP/rpm-tmp.60754
+ cd /kolab/RPM/TMP
+ set +x
+----------------------------------Warning------------------------------------+
| This OpenPKG package is of class
JUNK.
|
| It is in development state and still not even ready for evaluation. |
| Do not use it at all, as it is definitely unstable and incomplete. |
| Only CORE and BASE class packages are production
grade.
|
+-----------------------------------------------------------------------------+
+ cd /kolab/RPM/TMP
+ rm -rf horde-kolab-20070319
+ /kolab/lib/openpkg/shtool mkdir -f -p -m 755 horde-kolab-20070319
+ cd horde-kolab-20070319
+ /kolab/lib/openpkg/gzip -dc /kolab/RPM/SRC/horde-kolab/horde-kolab-20070319.tar.gz
+ /kolab/lib/openpkg/tar -xf -
+ STATUS=0
+ '['; 0 -ne 0 ']';
+ exit 0
Executing(%build): env -i /kolab/lib/openpkg/bash --norc --noprofile --posix -e /kolab/RPM/TMP/rpm-tmp.44967
+ cd /kolab/RPM/TMP
+ cd horde-kolab-20070319
+ exit 0
Executing(%install): env -i /kolab/lib/openpkg/bash --norc --noprofile --posix -e /kolab/RPM/TMP/rpm-tmp.44967
+ cd /kolab/RPM/TMP
+ cd horde-kolab-20070319
+ rm -rf /kolab/RPM/TMP/horde-kolab-20070319-root
+ /kolab/lib/openpkg/shtool install -d /kolab/RPM/TMP/horde-kolab-20070319-root/kolab/var/kolab/www/horde
+ /kolab/lib/openpkg/shtool install -d /kolab/RPM/TMP/horde-kolab-20070319-root/kolab/etc/kolab/templates
+ cd horde/config
+ for fl in '*.dist'
+ cp conf.php.dist conf.php
+ for fl in '*.dist'
+ cp hooks.php.dist hooks.php
+ for fl in '*.dist'
+ cp mime_drivers.php.dist mime_drivers.php
+ for fl in '*.dist'
+ cp motd.php.dist motd.php
+ for fl in '*.dist'
+ cp nls.php.dist nls.php
+ for fl in '*.dist'
+ cp prefs.php.dist prefs.php
+ for fl in '*.dist'
+ cp registry.php.dist registry.php
+ cd ../..
+ cp -r horde /kolab/RPM/TMP/horde-kolab-20070319-root/kolab/var/kolab/www
+ /kolab/lib/openpkg/shtool install -c -m 644 -e 's; l_susr ;root;g9; -e
's; l_sgrp ;root;g9; -e 's; l_suid ;0;g' -e 's; l_sgid ;0;g' -e
's; l_musr ;kolab;g39; -e 's; l_mgrp ;kolab;g39; -e 's; l_muid ;19414;g39; -e
's; l_mgid ;19414;g39; -e 's; l_rusr ;kolab-r;g' -e
's; l_rgrp ;kolab-r;g' -e 's; l_ruid ;19415;g39; -e 's; l_rgid ;19415;g39;
-e 's; l_nusr ;kolab-n;g' -e 's; l_ngrp ;kolab-n;g' -e
's; l_nuid ;19416;g39; -e 's; l_ngid ;19416;g39; -e 's; l_prefix ;/kolab;g'
-e 's; l_prefix_static ;/kolab;g'
/kolab/RPM/SRC/horde-kolab/horde-kolab-conf.template
/kolab/RPM/TMP/horde-kolab-20070319-root/kolab/etc/kolab/templates
+ /kolab/lib/openpkg/shtool install -o kolab-n -g kolab-n -c -m 644 -e
's; l_susr ;root;g9; -e 's; l_sgrp ;root;g9; -e 's; l_suid ;0;g' -e
's; l_sgid ;0;g' -e 's; l_musr ;kolab;g39; -e 's; l_mgrp ;kolab;g39; -e
's; l_muid ;19414;g39; -e 's; l_mgid ;19414;g39; -e 's; l_rusr ;kolab-r;g'
-e 's; l_rgrp ;kolab-r;g' -e 's; l_ruid ;19415;g39; -e
's; l_rgid ;19415;g39; -e 's; l_nusr ;kolab-n;g' -e
's; l_ngrp ;kolab-n;g' -e 's; l_nuid ;19416;g39; -e 's; l_ngid ;19416;g39;
-e 's; l_prefix ;/kolab;g' -e 's; l_prefix_static ;/kolab;g'
/kolab/RPM/SRC/horde-kolab/hooks.php
/kolab/RPM/TMP/horde-kolab-200703 | |