This forum is no longer active. Please post your questions to our new community site
trac-admin not working on Amazon AMI
|
|
Hi – I am getting a series of errors when trying to run trac-admin on my Amazon AMI. I have gone to the installation directory (/opt/bitnami/) and typed . scripts/setenv.sh . I have then tried to execute /opt/bitnami/trac/bin/trac-admin help (which should just bring up help file). Whether I do help or any other command, including initenv, I get a series of “command not found” errors e.g. line 3: requires: command not found. I think I have set all permissions correctly. Help! Thanks Nick |
|
|
Hi, Try to run the trac-admin tool with the python binary:
|
|
|
I get: -bash: bq.$: command not found Nick |
|
|
Sorry, have done . scripts/setenv.sh first and now get: /usr/bin/python: /opt/bitnami/common/lib/libz.so.1: no version information available (required by /usr/bin/python) |
|
|
Hi, Could you check the first line in the trac-admin script? If it is “#!/usr/bin/python”, could you try to modify to “#!/opt/bitnami/python/bin/python”? |
|
|
Script contains #!/opt/bitnami/python/bin/python Nick |
|
|
Thanks for reporting it. We will investigate this issue. |
|
|
Hi, I have tested executing: . /opt/bitnami/scripts/setenv.sh and it works. Could you try it again? the bq.$ that you instruced was not part of the command. In any case we will investigate the cause of the error related to zlib and /usr/bin/python. |
|
|
The Mac OS X stack has a similar problem on Snow Leopard. The setenv.sh fix didn’t help, but changes the error a bit. On the first run (before setenv.sh) it launches my X11 server and the script hangs until I shut down the server (no windows open though, and it’s not an xhost problem since things like xclock work). On the second run (after setenv.sh) it doesn’t try X11. On my other machine (running Leopard) it fails similarly but I don’t recall the error about /var/mail. Here’s the transcript:
|
|
|
Actually, it’s pretty much the same on Leopard as Snow Leopard, except it didn’t try to do anything with X11:
|
|
|
Please try the following:
or replace the following in the /Applications/trac-0.11.6-1/trac/bin/trac-admin:
with
and then run the follwing commands:
We will fix this issue in the next version. I hope it helps. |
|
|
Thanks for the reply. I tried both fixes and I’m a little confused by the result — I’m sure this illustrates my lack of python experience, so forgive me for that. For the first solution, trac-admin with no args spits out the help as expected, which is encouraging, but if I try to run a command, it goes into an interactive mode using the command in the path, and then fails because the path doesn’t exist!
It does the same thing if I use “bogus” as the comment, for example.
For the second suggestion, I assume I should replace the “/opt/bitnami” path with my /Applications/trac path, but I tried it both ways to be sure, and with my correct path it behaves the same as the above description:
|
|
|
Hi, Is it possible that you are not the using trac-admin tool correctly?
Usage: trac-admin </path/to/projenv> [command [subcommand] [option …]] Before the command, you need to include the path to the project. For instance if you want to create a new project you can execute:
and you will be prompted to enter more information about the settings for the new project. Also you could use:
and in the trac-admin console execute initenv. Most of the trac-admin ommands requires the project to exist, so if ‘bogus’ doesn’t exist, the resync command will fail. Please let us know if this is what if happening. Thanks. |
|
|
Oh that’s embarrassing — you’re right, I was not using trac-admin correctly! I haven’t used it much before and ran into this when it complained about needing a resync, and I was omitting the path. I was confused when it interpreted my single argument (which I was thinking was a command) as a repository instead. Thanks for setting me straight. When used correctly, trac-admin with the fix to the file as suggested above (putting in /usr/bin/env) works for me now, so I’m in business. Thanks again! |
|
|
(Correction, I should have said it was interpreting my single argument as a (trac) project, not repository. Also, I wanted to add that this testing has been on Mac OS X 10.6.3, in case you’re tracking that.) |

