[Pgreet-users] Re: Problems encountered and the things I did to fix them

[Ethan B. <bur...@ka...>]

Imtiaz,

    Good work.  I remember having to do the "use lib" bit too.  Not fun,
but thankfully there aren't many places it has to go.  You've definitely
come a bit farther than we did.  (I never got it to put the messages in
the queue, and never got the daemon to start up.)

    As for your remaining problem, I see that we have suexec support
turned off on your domains.  suexec is a cgi processing feature that
makes all CGI scripts work such that they are executed as your user,
instead of the www user.  I suspect that turning suexec on for the
domain you're using might take care of it.

    Just let us know what domain you're using, and we can give it a whirl.

    Worth noting for the list and dev folks, the install we're doing is
without root privileges, as we're doing it to a shared hosting account.
 The host has installed all of the required perl modules, of course
minus pgreet itself.  Thus the "use lib" and other system username
customizations being necessary.

Cheers,

~Ethan B.

-- 
----------------------------------
 Ethan Burnside - Founding Member
 Kattare Internet Services
 WWW: http://www.kattare.com
 E-mail: bur...@ka...
----------------------------------



Quoting Imtiaz A Khan <kha...@gm...>:

> Here are some of the issues I faced and resolved while setting up
> Pgreet
> 
>    1. Once the installation (Install.pl) is complete I ran
>       PgreetConftest and recieved an error about missing Pgreet.pm I
>       added it by using the following in all cgi/perl scripts in the
> distro:
>           * *use lib '/home2/w/weathers/pg/pgreet/lib/'; *
>           * here /home2/w/weathers is my home directory and pg is
> the
>             directory into which I checked out pgreet from CVSNext
> on
>             running the config testI recieved a list of errors for
>             datadir, cgidir, tempdir etc. It seems that the
> install.pl
>             does not take care of writing a clean pgreet.conf.
>    2. Next on running the config testI recieved a list of errors for
>       datadir, cgidir, tempdir etc. It seems that the install.pl
> does
>       not take care of writing a clean pgreet.conf.
>           * replaced cgi-dir with my value of cgi-dir (some folks
> want
>             to use an alternate to cgi-bin for security reasons)
>           * the conf dir has an extra /conf at the end remove that
>           * the images URL has a pgreet/images by default change that
> to
>             where you installed pgreet in my case /ecards/images
>           * the temp folder for sessions is /tmp it might not be
>             accessible to user accounts change that to a folder in
> your
>             home which has rights for Apache to write to (777 would
> be
>             great to start with and whittle it down to saner
> permission
>             levels after testing)
>           * the log folder similarly is /var/log whcih will not work
> for
>             some OS platforms (I changed this also to a user
> directory)
> 
>    3. on startup pgreet daemon complains of *strict refs in pgreetd
> on
>       line 1000*. Not sure what that implies but I commented out use
>       strict in pgreetd and it was able to start up.
>    4. Then I got an error with regards to session files. Pgreet was
>       unable to create state files. For that the permissions on TEMP
>       directory had to be changed
>    5. Now I got  *Not found 'pgreet_template.epl'* which is not in
> the
>       distribution but is available when you do a CVS checkout. Even
>       then it had to be manually copied to the templates folder from
> the
>       source folder.
>    6. At this point everything seemed ok I was able to pull it up in
> the
>       browser and customize a card and click send. Once that was
> done
>       again it all crashed as I started getting these erors in my
> pgreet
>       log:
>       /Oct 28 00:17:20 pgreetd [19096] shutdown by signal - Error
>       getting name to temp file from template pgreet-tmpfile-XXXXXX:
>       Parent directory (.) is not writable
>        at /home2/w/weathers/bin/pgreetd line 656
>       /Am stuck here as now it all shows up etc but since pgreetd is
>       dying no card notifications are going out. I tried looking at
> the
>       permissions and I guess thats where the problem lies. The
> session
>       files are being written by www (the apache user) with
> permission
>       622 and my pgreet daemon is set to run as user weathers.
> Looking
>       for the setting where I could maybe change permissions on the
>       sessions files so that pgreetd can write to those and process
> them
>       (I'm thinking this is it)/
>       /
> 
> Warm Regards
> Imtiaz
>