Queue Worker Failing w/ Illuminate/Foundation Error - laravel

I am using supervisor to run a queue work and it is failing with the following error:
Parse error: parse error, expecting `'&'' or `"variable (T_VARIABLE)"' in /Users/chris/Development/project/repo/vendor/laravel/framework/src/Illuminate/Foundation/helpers.php on line 475
This error shows up repeatedly in the worker logs.
Has anyone ever encountered this? Any idea what the issue might be?

So it turns out the Supervisor works were using a different version of PHP than my CLI and web server. I updated the php path to the correct bin in the worker config and all is well.

Related

Kafka server start is not working on command line

If i try to run below command in order to start kafka server on CMD (Command Propmt)
C:\kafka_2.12-0.11.0.0\bin\windows\kafka-server-start.bat ..\..\config\server.properties
I get error as below
Question:
I just started to learn kafka so if i try to run above command i can not start kafka server.Where i miss exactly ? I still get error despite i delete log files.How can i start kafka server ?
Any help will be appreciated.
Thanks.
See if the log.dirs configuration is wrong
I had the same problem. I restarted my machine thinking the file in contention will be cleared after restart. That didn't help. So, I cleared out the entire tmp\kafka-logs directory and restarted the kafka server and it worked fine.

Trouble installing google assistant on a raspberry pi 3

I am getting the following error when I run google-assistant-demo
OpenAlsaHandle PcmOpen: No such file or directory
[4571:4583:ERROR:audio_input_processor.cc(756)] Input error
ON_MUTED_CHANGED:
{'is_muted': False}
ON_START_FINISHED
ON_ASSISTANT_ERROR:
{'is_fatal': True}
[4571:4586:ERROR:audio_input_processor.cc(756)] Input error
ON_ASSISTANT_ERROR:
{'is_fatal': True}
I got this error a couple of times, assuming you have done everything described here and it is working: https://developers.google.com/assistant/sdk/prototype/getting-started-pi-python/configure-audio
Do a sudo reboot to make sure there aren't multiple instances of the google-assistant-demo running.
Then if you are running the google-assistant-demo from a script (either start-up or manually) try running it without a sudo prefix, that fixed my problem!
See my post here for more detail about how I got it running smoothly from start-up
Its an error due to improper alsa.conf configuration. You need to change it according to your audio setup.

Installing Spark on ec2 gives error EC2ResponseError: 403 Forbidden

I was following this guide for installing spark on ec2.But getting following error while launching cluster:
ERROR:boto:403 Forbidden
I ran into this problem and got around it by using a "-w 600", which basically says wait for 600 second. Apparently, there is some housekeeping that the process needs more time on.
Ok I found out here that you have to set the privilege of the user (the user from which you got your AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY) to the value AmazonEC2FullAccess
This should solve your problem for most of you !

facing No xulrunner found running on port=5000 error when trying to access console from ssu app

I'm trying to run ssu APP https://github.com/wesabe/ssu on ubuntu 10.04. bin/server command executed without any issues but when I am trying to access console [script/console], I am facing below error :
No xulrunner found running on port=5000!
I have verified all the services that are running in the system, In that list I could not find xulrunner service running on 5000 port.
Can anyone please let me know what might be the possible solution to fix this issue.
Thank you
I found the problem, below mentioned fix as resolved the issue :
In application/chrome/content/wesabe/download/Controller.coffee
changed Server = require 'io/http/Server'
to
Server = require 'io/http/server'

Cloudfoundry step up error - caused by Chef

I followed the Readme on https://github.com/cloudfoundry/vcap
It should be work fine...
but I got the error like this :
Does anyone know what's going on?
I run on Ubuntu10.04 ...
I have not encountered this problem with the latest version of VCAP, how long has it been since you updated the copy of the VCAP source on the Ubuntu instance?
Can you also post the configuration file you are using? if any.

Resources