Manual Apache Install

[Tom]

Hey there!

I've done an install manually - no docker capability for prod here unfortunately.

Struggled a bit with nginx with refreshing a page and hitting an error. So moved to apache, and most things are working well.

My problems:

* I'm honestly not sure how to install/manually create the php-worker. I've tried just making another virtual host using the github for the worker, but it just give the error:
Could not execute action: THttpClient: Could not connect to localhost:9092 in /var/www/fusio/html/vendor/fusio/impl/src/Worker/Action/WorkerAbstract.php on line 84",Specifically - Service unavailable - Worker returned no result

--There wasn't really any info on creating a worker, just a link to the github files. Or maybe i'm missing something.
Everything is on one server for this.

* When I add an action or a user, they dont appear in the list. I can even clear my cache out and nothing. If I search by name it appears, and if I clear the search, it shows everything but the one i just made. Oddly enough, after a while (maybe on apache restart) it begins to show up. What might I have messed up there?
The docker version i have as a dev server works AWESOME. You all have spent a lot of time on this. It's missing a little polish here and there but is AWESOME. We have 3 devs over here, and we already are grasping the basics.

[Tom]

Errors in the 9092 virtual host:

[Fri Jun 23 14:23:34.981582 2023] [proxy_fcgi:error] [pid 84330:tid 84511] [client ::1:60124] malformed header from script 'index.php': Bad header: \x80\x01

[Fri Jun 23 14:23:34.981624 2023] [proxy_fcgi:error] [pid 84330:tid 84511] [client ::1:60124] AH01070: Error parsing script headers

[Fri Jun 23 14:23:34.981630 2023] [proxy_fcgi:error] [pid 84330:tid 84511] (22)Invalid argument: [client ::1:60124] AH01075: Error dispatching request to :9092:

[Fri Jun 23 14:23:36.120994 2023] [proxy_fcgi:error] [pid 84544:tid 84589] [client ::1:60128] malformed header from script 'index.php': Bad header:

[Fri Jun 23 14:23:36.121049 2023] [proxy_fcgi:error] [pid 84544:tid 84589] [client ::1:60128] AH01070: Error parsing script headers

[Fri Jun 23 14:23:36.121055 2023] [proxy_fcgi:error] [pid 84544:tid 84589] (22)Invalid argument: [client ::1:60128] AH01075: Error dispatching request to :9092:

[Tom]

One additional find. The php-fpm on the worker reveals some errors pertaining to properties on a stdClass. Each instance is me trying to access $request from "Fusio\Worker\Generated\Request"
. It's almost like the request is not available to the worker.

[Christoph Kappestein]

Hi Tom,

since I have only answered you via mail, I will post this here also for other users.

--

this looks indeed like there is a problem with the FCGI connection. So if you only use the PHP-Worker you may also consider to use a PHP class or file directly without the worker if all your code lives on one server, this should greatly simplify the setup since you dont need the worker communication. Most users use the worker setup only if they want to support different languages.

If you still want to get this to work I would recommend to create a dedicated port or sub domain where the worker lives. For this you can either directly use our docker image s.

https://github.com/apioo/fusio-worker-php/blob/main/Dockerfile

or you can of course also manually host the worker, in this case you need to use the public/ folder as document root. Note in our docker image we use "php:8.1-apache" as module so we dont use FCGI, but in general this should not be an issue.

So I hope I could help you a little by providing some ideas to solve your problem.

best regards

Christoph

[Tom]

Thanks Christoph. I've since gone the Docker route, but encounter an issue. It seems to be the server caches things in apps/fusio. I'm wondering if this is a failure in my setup.

Ex) If I edit an action - the new action code appears in the worker container public/actions. However, in the browser, if I change navigation and go back in, it still pulls up the old code prior to my changes.

Same thing happens when deleting actions/users, they still show up for a long while.

What's possibly causing this behavior? I've locked it down to not being browser (clearing cache on browser does nothing). Would love to fix as it's really putting snags in editing. Otherwise everything seems to be working like a champ!

[Tom]

It also seems user based... If I change an action or route, it looks the same as before if i leave and come back, but if my buddy accesses it who has not seen it yet, they see all of the new changes.

[Christoph Kappestein]

Hi Tom,

this sounds indeed like a problem with the Angular backend app, which version do you currently use, with the latest 4.0 version we have changed many aspects at the backend app so maybe this problem is then also solved?

best regards

Christoph