[gentoo-user] problems running doxygen from cron

[gentoo-user] problems running doxygen from cron

[Dirk Uys]

Hi

I have a problem when running doxygen from a cron job. It seems like
doxygen is simply aborting at an arbitrary point during execution. I
tried to search on the internet, but could not find anything similar
reported.

I have the following script:

<script>
#!/bin/bash
echo `date` >> /home/user/cron.log
/usr/bin/svn update /home/user/source/
/bin/cp /home/user/live_doc /home/user/source/

echo "====== Start Doxygen ======"

/usr/bin/doxygen /home/user/source/live_doc

echo "====== Doxygen completed ======"

/bin/cp -R /home/user/source-doxy/html/* /home/www/source-doxy/

echo "====== Copy completed ======"
</script>

My cron entry is
45 * * * * /home/user/script.sh >> /home/user/debug.log

When I run the script from the command line it works fine and doxygen
executes successfully, but when cron executes the script, doxygen
simply aborts at some point:

<snip from debug.log>
Parsing file /home/dcuys/vgd_m/gripentactics/source/titles/grdetectionlist.cpp...
Preprocessing /home/dcuys/vgd_m/gripentactics/source/titles/grdetectionlist.h...
Parsing file /home/dcuys/vgd_m/gripentactics/source/titles/grdetectionlist.h...
Preprocessing /home/dcuys/vgd_m/gripentactics/source/titles/grdetectionvolumes.cpp...
Parsing file /home/dcuys/vgd_m/gripentactics/source/titles/grdetectionvolumes.cpp...
Preprocessing /home/dcuys/vgd_m/gripentactics/source/titles/grdetectionvolumes.h...
Par
====== Doxygen completed ======
====== Copy completed ======
</snip from debug.log>

I'm using vixie-cron-4.1-r10 and doxygen-1.5.4

Regards
Dirk

Re: [gentoo-user] problems running doxygen from cron

[Alex Schuster]

Dirk Uys wrote:

> I have a problem when running doxygen from a cron job. It seems like
> doxygen is simply aborting at an arbitrary point during execution. I
> tried to search on the internet, but could not find anything similar
> reported.
[...]
> My cron entry is
> 45 * * * * /home/user/script.sh >> /home/user/debug.log

I would add a " 2>&1" to the cron entry in order to get stderr output 
logged, too. Maybe there are error messages you are missing.

My cron problems usually come from the PATH being restricted, anthough 
this shoudl not matter in your case with the script, I think. Anyway, I'd 
start it with "#!/bin/bash -l" in order to open a login shell, and I 
would include the "env" command in the script so I can spot differences 
in the environment.

Just some ideas,

	Wonko

Re: [gentoo-user] problems running doxygen from cron

[Dirk Uys]

On Sat, Feb 14, 2009 at 5:22 PM, Alex Schuster <wonko@wonkology.org> wrote:
> Dirk Uys wrote:
>
>> I have a problem when running doxygen from a cron job. It seems like
>> doxygen is simply aborting at an arbitrary point during execution. I
>> tried to search on the internet, but could not find anything similar
>> reported.
> [...]
>> My cron entry is
>> 45 * * * * /home/user/script.sh >> /home/user/debug.log
>
> I would add a " 2>&1" to the cron entry in order to get stderr output
> logged, too. Maybe there are error messages you are missing.
>
> My cron problems usually come from the PATH being restricted, anthough
> this shoudl not matter in your case with the script, I think. Anyway, I'd
> start it with "#!/bin/bash -l" in order to open a login shell, and I
> would include the "env" command in the script so I can spot differences
> in the environment.
>
> Just some ideas,
>
>        Wonko

Thanks! I actually solved this one some time ago.

It turned out that because I omitted "2>&1" the stderr stream weren't
created. The program tried to write to stderr and terminated because
it didn't exist. Strange, but that's what happened.

Regards
Dirk