php Could not open input file: symfony

[seibs...@gmail.com]

Hi there, admittedly I'm out of my depth trying to get AtoM installed and working for some users where I work, I believe I've followed the install instructions correctly, but when I get to the gearman configuration section, I'm entering:

php symfony jobs:worker

And I'm getting

Could not open input file: symfony

OS is Ubuntu 18.04.3, freshly built for this purpose.  The AtoM server and the Gearman service are all on the same machine.

Thanks in advance!

[Karl Goetz]

Hi,
You are probably in the wrong directory.

try running `pwd` to find your current location and `ls -lh` to see what files there are.

thanks,

--
Karl Goetz
Technical Services Officer - eResearch, Information Technology Services
University of Tasmania & Tasmanian Partnership for Advanced Computing

Mail: University of Tasmania, Private Bag 69, Hobart, Tasmania 7001
Delivery: TT Flynn Street, Sandy Bay, Tasmania 7005



University of Tasmania Electronic Communications Policy (December, 2014).
This email is confidential, and is for the intended recipient only. Access, disclosure, copying, distribution, or reliance on any of it by anyone outside the intended recipient organisation is prohibited and may be a criminal offence. Please delete if obtained in error and email confirmation to the sender. The views expressed in this email are not necessarily the views of the University of Tasmania, unless clearly intended otherwise.

[Dan Gillean]

Hi there, 

I suspect that Karl is right - so far every time I have seen that specific error, it is because the command is not being run from the root AtoM installation directory - which, if you have followed our recommended installation instructions, is typically /usr/share/nginx/atom. 

All commands that begin with php symfony should be run from this location for them to succeed - Symfony is the PHP framework that we used to build AtoM, meaning that trying to invoke Symfony commands from outside of AtoM's directory returns that error. You can also try to change directly to the root installation directory with: 

• cd /usr/share/nginx/atom

And then try running the jobs task again. 

A couple more general resources that might help if you are new to working in the command-line: 

• CLI 101: a brief set of slides I put together to introduce users to some basic unix/linux commands for navigation, file management, etc. If you do an online search for "command-line cheat sheet" or "command-line tutorial" you will find many other resources as well
• https://www.slideshare.net/accesstomemory/commandline-101  
  
• AtoM CLI tasks: this will introduce you to some of the most commonly used command-line tasks supported by AtoM, several of which you will use during the installation and maintenance of your new AtoM site. See a full list of CLI tasks in our documentation here. 
• https://www.slideshare.net/accesstomemory/atoms-command-line-tasks-an-introduction  
  
• Troubleshooting page: I would say that 85% of all technical issues I see posted in this forum can regularly be solved with help from the guidance found on this page. Hopefully it will be of use to you as well!
• https://www.accesstomemory.org/docs/latest/admin-manual/maintenance/troubleshooting/  

Hope this helps! Let us know how it goes. 

Cheers, 

Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
604-527-2056

@accesstomemory

--
You received this message because you are subscribed to the Google Groups "AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/9f96b668-53c5-432e-8a5c-54ebc7658212%40googlegroups.com.

[seibs...@gmail.com]

Thank you for the assistance.  It turns out that it was qa mixture of running it in the wrong place and permissions to the directory that prevented things from working.

Thanks!