|
|
| kolab-2.2-beta2; OpenPKG error:
unexpected EOF |

|
2007-10-28 12:09:54 |
Hello all.
The installation process compiled OpenPKG OK, but when
OpenPKG itself is
called to compile the res of the Kolab packages, the
following error comes
up:
--------------------
root sbs01:/kolab/sources/development/2.2-beta2#
./install-kolab.sh -H -F
2>&1 | tee kolab-install.log
Kolab installation tag (TAG): kolab
Kolab installation prefix (PREFIX): /kolab
Kolab version (KOLAB_VERSION): 2.2-beta2
Kolab user name (USER): kolab
Kolab user base UID (KID): 19414
Kolab restricted UID (KID): 19415
Kolab non-priviledged UID (KID): 19416
Received no instructions. Trying to determine required
action...
Found an OpenPKG environment. Assuming upgrade...
/kolab/lib/openpkg/openpkg: command substitution: line 298:
unexpected EOF
while looking for matching `''
/kolab/lib/openpkg/openpkg: command substitution: line 300:
syntax error:
unexpected end of file
/kolab/lib/openpkg/openpkg: line 298: exec:
shtool:path:Error:: not found
-------------------
It would appear that there is a missing quotation mark
somewhere. In case you
need it, line 298 of "/kolab/lib/openpkg/openpkg"
is:
-------------------
eval "exec $ $ ${1+"$ "}"
-------------------
In fact, that's the last line of the file. I ran the script
through a bash
syntax checker (via plugin for VIM), but it all looks OK.
Please advise. TIA!
-Alan Murrell
_______________________________________________
Kolab-users mailing list
Kolab-users kolab.org
https:
//kolab.org/mailman/listinfo/kolab-users
|
|
| Re: kolab-2.2-beta2; OpenPKG error:
unexpected EOF |

|
2007-10-28 12:15:44 |
Oh, system is Ubuntu 7.10 (Gutsy) using gcc-4.1 to have
compiled the OpenPKG
system, if that is of any consequence.
-Alan Murrell
_______________________________________________
Kolab-users mailing list
Kolab-users kolab.org
https:
//kolab.org/mailman/listinfo/kolab-users
|
|
| Re: kolab-2.2-beta2; OpenPKG error:
unexpected EOF |

|
2007-10-29 05:35:17 |
* Alan Murrell <lists murrell.ca> [20071028
18:10]:
> The installation process compiled OpenPKG OK, but when
OpenPKG itself is
> called to compile the res of the Kolab packages, the
following error comes
> up:
>
> --------------------
> root sbs01:/kolab/sources/development/2.2-beta2#
./install-kolab.sh -H -F
> 2>&1 | tee kolab-install.log
>
> Kolab installation tag (TAG): kolab
> Kolab installation prefix (PREFIX): /kolab
> Kolab version (KOLAB_VERSION): 2.2-beta2
> Kolab user name (USER): kolab
> Kolab user base UID (KID): 19414
> Kolab restricted UID (KID): 19415
> Kolab non-priviledged UID (KID): 19416
>
> Received no instructions. Trying to determine required
action...
> Found an OpenPKG environment. Assuming upgrade...
Is this really intended to be an upgrade to an existing
(possibly
broken) installation?
If no, please remove the old install in /kolab
If yes, please try the updated install-kolab.sh:
http://kolab.org/cgi-bin/viewcvs-ko
lab.cgi/*checkout*/server/install-kolab.sh
Regards,
Thomas
--
thomas intevation.de - http://intevation.de/~t
homas/ - OpenPGP key: 0x5816791A
Intevation GmbH, Osnabrueck - Register: Amtsgericht
Osnabrueck, HR B 18998
Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr.
Jan-Oliver Wagner
_______________________________________________
Kolab-users mailing list
Kolab-users kolab.org
https:
//kolab.org/mailman/listinfo/kolab-users
|
|
| Re: kolab-2.2-beta2; OpenPKG error:
unexpected EOF |
  Canada |
2007-10-29 18:16:54 |
> Is this really intended to be an upgrade to an existing
(possibly
> broken) installation?
No, fresh install of kolab2.2-beta2 (no previous
installation). The
message about the "Assuming upgrade" was just
subsequent runs of the
install-kolab.sh script (since OpenPKG installed OK, it
detected the
OpenPKG environment)
>
> If no, please remove the old install in /kolab
>
> If yes, please try the updated install-kolab.sh:
> http://kolab.org/cgi-bin/viewcvs-ko
lab.cgi/*checkout*/server/install-kolab.sh
I deleted everything in the /kolab directory 9except where I
downloaded
the sources)and also grabbed the updated install-kolab.sh
script you
refenced above. I get exactly the same error:
(immediately after the successful installation of the
OpenPKG environment)
----------
/kolab/lib/openpkg/openpkg: command substitution: line 298:
unexpected EOF
while looking for matching `''
/kolab/lib/openpkg/openpkg: command substitution: line 300:
syntax error:
unexpected end of file
/kolab/lib/openpkg/openpkg: line 298: exec:
shtool:path:Error:: not found
----------
Let me know if you need any further information.
TIA for your help and suggestions.
-Alan Murrell
_______________________________________________
Kolab-users mailing list
Kolab-users kolab.org
https:
//kolab.org/mailman/listinfo/kolab-users
|
|
| Re: kolab-2.2-beta2; OpenPKG error:
unexpected EOF |
  Canada |
2007-10-29 18:54:48 |
OK, I have made a bit of progress. It seems the BASH shell
installed by
OpenPKG does not have the same rules for quotes as others.
On line 298, I
replaced the double quotes on either end with single quotes,
like this:
----------
eval 'exec $ $ ${1+"$ "}'
----------
and re-ran the install-kolab.sh script. The error about EOF
due to
missing matching `'' is gone, but the error about path noth
found remains:
----------
/kolab/lib/openpkg/openpkg: line 298: exec:
shtool:path:Error:: not found
----------
Please advise
-Alan Murrell
_______________________________________________
Kolab-users mailing list
Kolab-users kolab.org
https:
//kolab.org/mailman/listinfo/kolab-users
|
|
| Re: kolab-2.2-beta2; OpenPKG error:
unexpected EOF |
  Germany |
2007-10-30 03:00:00 |
Alan Murrell <lists murrell.ca> writes:
> Hello all.
>
> The installation process compiled OpenPKG OK, but when
OpenPKG itself is
> called to compile the res of the Kolab packages, the
following error comes
> up:
>
> --------------------
> root sbs01:/kolab/sources/development/2.2-beta2#
./install-kolab.sh -H -F
> 2>&1 | tee kolab-install.log
Are there any errors in your "kolab-install.log"?
This looks like
OpenPKG is not installing correctly.
>
> Kolab installation tag (TAG): kolab
> Kolab installation prefix (PREFIX): /kolab
> Kolab version (KOLAB_VERSION): 2.2-beta2
> Kolab user name (USER): kolab
> Kolab user base UID (KID): 19414
> Kolab restricted UID (KID): 19415
> Kolab non-priviledged UID (KID): 19416
>
> Received no instructions. Trying to determine required
action...
> Found an OpenPKG environment. Assuming upgrade...
> /kolab/lib/openpkg/openpkg: command substitution: line
298: unexpected EOF
> while looking for matching `''
> /kolab/lib/openpkg/openpkg: command substitution: line
300: syntax error:
> unexpected end of file
> /kolab/lib/openpkg/openpkg: line 298: exec:
shtool:path:Error:: not found
> -------------------
>
> It would appear that there is a missing quotation mark
somewhere. In case you
> need it, line 298 of
"/kolab/lib/openpkg/openpkg" is:
>
> -------------------
> eval "exec $ $
${1+"$ "}"
> -------------------
You could also add a line
echo "exec $ $ ${1+"$ "}"
to identify what command should be ran there. This might
give us some
more information.
Cheers,
Gunnar
>
> In fact, that's the last line of the file. I ran the
script through a bash
> syntax checker (via plugin for VIM), but it all looks
OK.
>
> Please advise. TIA!
>
> -Alan Murrell
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users kolab.org
> https:
//kolab.org/mailman/listinfo/kolab-users
--
______ http://kdab.com
_______________ http://kolab-konsortium.c
om _
p rdus Kolab work is funded in part by KDAB and the
Kolab Konsortium
____ http://www.pardus.de
_________________ http://gunnarwrobel.de _
E-mail : p rdus.de Dr. Gunnar
Wrobel
Tel. : +49 40 432 72335
Bundesstrasse 29
Fax : +49 40 432 70855 D-20146
Hamburg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~
>> Mail at ease - Rent a kolab groupware server at
p rdus <<
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~
_______________________________________________
Kolab-users mailing list
Kolab-users kolab.org
https:
//kolab.org/mailman/listinfo/kolab-users
|
|
| Re: kolab-2.2-beta2; OpenPKG error:
unexpected EOF |
  Germany |
2007-11-01 06:16:18 |
On Tuesday 30 October 2007 09:00, Gunnar Wrobel wrote:
> to identify what command should be ran there. This
might give us some
> more information.
Also try running the script with "bash -x" to find
out what
the called command is that leads to the problem.
--
Managing Director - Owner: www.intevation.net (Free
Software Company)
Germany Coordinator: fsfeurope.org. Coordinator:
www.Kolab-Konsortium.com.
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB
18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr.
Jan-Oliver Wagner
_______________________________________________
Kolab-users mailing list
Kolab-users kolab.org
https:
//kolab.org/mailman/listinfo/kolab-users
|
|
| Re: kolab-2.2-beta2; OpenPKG error:
unexpected EOF |

|
2007-11-01 09:24:45 |
Sorry I didn't get a chance to follow up on the other
suggestions before now,
but I made a breakthrough, based on Bernhard's suggestion
(below) and I
believe I have the solution. I am currently re-compiling
"fresh" to see if
indeed the problem I solved.
Now for the (relatively long) explanation of what I believe
the problem to
be...
On Thursday 01 November 2007 04:16:18 Bernhard Reiter
wrote:
> Also try running the script with "bash -x" to
find out what
> the called command is that leads to the problem.
I had initially received errors about there not being enough
room in my
$TMPDIR and that it needed a certain amount of room. I have
the /kolab
partition on a seperate disk, so I created a /kolab/tmp
directory and
exported the $TMPDIR variable there. By adding the
"-x" to the "bash" line
at the top of the '/kolab/lib/openpkg/openpkg' script, it
spat out a lot of
output, particularly about not being able to create/read
certain files it was
expecting to find in $TMPDIR. I suddenly realized that
OpenPKG had been
coipled by the system's "root" user, but that the
Kolab packages were likely
being compiled under OpenPKG as one of the "Kolab"
users, and that when I
created '/kolab/tmp', I had not modified the permissions to
make the
directory world writeable, which I then created.
Before I blew away the existing OpenPKG installation, I ran
the installation
script and it didn't throw out any errors. I stopped it
from running, blew
everything (except the sources) away and am currently
compiling fresh.
Will post about any further errors, or if successful, will
also do so, so as
to "close" this issue.
Thanks again to all who have (thus far) taken their time to
help me with this.
-Alan Murrell
_______________________________________________
Kolab-users mailing list
Kolab-users kolab.org
https:
//kolab.org/mailman/listinfo/kolab-users
|
|
| Re: kolab-2.2-beta2; OpenPKG error:
unexpected EOF |

|
2007-11-02 22:43:17 |
OK, so I can now report that the installation went through
with no errors,
however I seem to have two problems, one of which may not be
Kola
related...
1.) the "snakeoil" certificate doesn't seem to
have been installed into
'/kolab/etc/apache/ssl.crt'. No indication that it was
generated.
Apache of course fails to start, unless I comment out the
lines in
'/kolab/etc/apache/apache.conf' that have to dowitht he SSL
certs. Is
there a way to generate them on the server?
2.) All te services are running, but I cannot connect to
any of them
(tried telnetting to ports 25, 110, and connecting to the
webserver on
port 80 from Firefox)
Thanks!
-Alan Murrell
_______________________________________________
Kolab-users mailing list
Kolab-users kolab.org
https:
//kolab.org/mailman/listinfo/kolab-users
|
|
| Re: kolab-2.2-beta2; OpenPKG error:
unexpected EOF |

|
2007-11-03 06:34:12 |
On 11/3/07, Alan Murrell <lists murrell.ca> wrote:
> OK, so I can now report that the installation went
through with no errors,
> however I seem to have two problems, one of which may
not be Kola
> related...
>
> 1.) the "snakeoil" certificate doesn't seem
to have been installed into
> '/kolab/etc/apache/ssl.crt'. No indication that it was
generated.
> Apache of course fails to start, unless I comment out
the lines in
> '/kolab/etc/apache/apache.conf' that have to dowitht he
SSL certs. Is
> there a way to generate them on the server?
/kolab/etc/kolab/kolab_sslcert.sh `hostname`
>
> 2.) All te services are running, but I cannot connect
to any of them
> (tried telnetting to ports 25, 110, and connecting to
the webserver on
> port 80 from Firefox)
>
Can you check if services are binded to the sockets, using
"netstat -a"
Is your hostaname, ip address configured into your /etc/host
file ?
> Thanks!
>
> -Alan Murrell
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users kolab.org
> https:
//kolab.org/mailman/listinfo/kolab-users
>
--
Alain Spineux
aspineux gmail com
May the sources be with you
_______________________________________________
Kolab-users mailing list
Kolab-users kolab.org
https:
//kolab.org/mailman/listinfo/kolab-users
|
|