I am creating a build from meteor source in a docker container.
It worked well so far (since last creation 1 or 2 weeks ago) but today an exception raises !
at /home/meteor/build/bundle/programs/server/boot.js:462:11
at /home/meteor/build/bundle/programs/server/boot.js:423:13
at Function.run (/home/meteor/build/bundle/programs/server/profile.js:510:12)
at /home/meteor/build/bundle/programs/server/boot.js:464:5
at Function.time (/home/meteor/build/bundle/programs/server/profile.js:309:28)
TypeError: Object.getOwnPropertyDescriptors is not a function
at insert (packages/mongo/collection.js:435:12)
at packages/autoupdate.js:189:3
at updateVersions (packages/autoupdate.js:125:20)
throw(ex);
/home/meteor/build/bundle/programs/server/node_modules/fibers/future.js:280
NB : log may be not ordered as I use ELK stack to handle it
What happened ? And what to do to solve it ?
FYI: the application works well locally (not builded)
Node 6 is currently default in alpine, that was the issue. I switch to node image which is safer (but bigger).
Related
I am currently trying to run through the example first application for Hyperledger Fabric here -> http://hyperledger-fabric.readthedocs.io/en/release-1.1/write_first_app.html
I am unable to get past calling node invoke.js
Originally I was getting the same error as this question Error invoking chaincode using Node.js SDK [TypeError: Cannot read property 'getConnectivityState' of undefined]
But after reverting to grpc#1.9.1 I get the following result:
I am able to do everything up to the node query.js method and that returns successfully but can't quite get past this.
Node version: 8.11.1
Docker Version:
fabric client section of package-lock.json
FYI: I am trying to run on Windows 10 mostly using the docker toolbox bash, or a separate git bash CLI.
Last piece of info!
Even though the invoke js command fails with the above error, I can see that the PUT command to couch db does go through and car10 has been successfully added.
If I check the docker logs for peer0.org1.example.com I see the following:
So did it actually work?
I am under the impression that my application on Bluemix is running an older (wrong) version of the code. I have made several updates and now the application doesn't deploy nor will it start. When I check the log files, I see some errors due to Express middleware changes that are no longer supported and should be replaced by external components, for example, replace bodyParser with body-parser. I have made all these changes replacing express.middlewarename with the new components according to this page: https://github.com/senchalabs/connect#middleware
However, I am still getting error messages in the log file when I try to deploy the application. The message is:
throw new Error('Most middleware (like ' + name + ') is no longer bundled with
Express and must be installed separately. Please see
https://github.com/senchalabs/connect#middleware.');
2017/4/5 午後2時42分48秒 ERR APP at Function.Object.defineProperty.get
(/home/vcap/app/node_modules/express/lib/express.js:107:13)
2017/4/5 午後2時42分48秒 ERR APP at Module._compile (module.js:409:26)
2017/4/5 午後2時42分48秒 ERR APP at Object.Module._extensions..js (module.js:416:10)
2017/4/5 午後2時42分48秒 ERR APP at Module.load (module.js:343:32)
I am able to run the application on my machine. If I download the code from the compile pipeline, it seems fine. However, I see some errors, which point to a line of code that is a comment or a blank line in my files.
All of these issues leads me to believe that Bluemix is trying to deploy a wrong version of code.
Does anyone know how can I fix it?
Thank you in advance.
First you have make sure your all node process is killed.
On linux you can check using : ps aux|grep node.
After that rebuild your npm. using "npm build" command.
Start you server it will work.
You can do a couple of things
1. Add a git commit tag as apart of your end point. Maven and other build tools have this capability and it good practice especially for micro service architectures. Spring has one and I would be surprised if node didn't have something similar. This is what I found with a brief search. [1]
2. Trying doing a cf d ${app_name} then re-push your app.
3. If you're using a manifest file or using the cf p command make sure you specify the path to the application being deployed. There are some other nuances with node on CF but you can also assign start scripts to the build pack when the app is being deployed.
I hope this helps.
[1] https://github.com/ktoso/maven-git-commit-id-plugin/
I have following problem:
I wrote a little homepage under Win10. All is fine but when I deploy my work in a Linux system I get the following message:
[2015-12-17 09:28:41] request.CRITICAL: Uncaught PHP Exception Twig_Error_Loader:
"The "/info/wwv/data/someone\vendor\symfony\symfony\src\Symfony\Bundle\FrameworkBundle/Resources/views" directory does not exist."
at /info/wwv/data/someone/vendor/twig/twig/lib/Twig/Loader/Filesystem.php line 94 [...]
I think there is some problem with the DIRECTORY_SEPARATOR or similar. The path exists and I can access it when I replace the backslashes with slashes.
Also my log is written in the directory app\logs instead real subdirectory app/logs.
Are you generating the cache on Windows and deploying the cache too instead of building it on the Linux server ? This is indeed not meant to work properly, due to differences between the OS.
Recent versions of Symfony allow to build the cache before deployment and copy it to the other server, but this does not work with Windows on one side and Linux on the other.
I had a similar issue. One day symfony 3.4 (on php7.2.16) stops working. After changing some path settings in AppKernel.php from '/' to '\\', everything works fine.
e.g.
public function getLogDir()
{
return dirname(__DIR__).'\\var\\logs';
}
It seems to be a windows-related issue with path-settings.
I had the same problem as my production server did not let me allocate enough ram to run composer and I had to run it locally.
Afterwards I got similar error (having wrong access path \ instead of / for linux)
Steps I took:
Replacing \\ with / in composer.json and composer.lock
Clearing the var/cache/*
I'm trying to deploy Kibana 4 to Azure Websites. I can't use bin/kibanta.bat file since Azure Websites uses start script in package.json to bootstrap application. I tried to update package.json start script to run bin\kibana.js file and environment variables in it. After that Azure starts running Kibana server but I'm getting this error: Uncaught ReferenceError: ZeroClipboard is not defined (http://kibana-site.azurewebsites.net/index.js?_b=5827:89458). Does anyone tried to make Kibana 4 run not using bin\kibana* files? Maybe I have to specify additional environment variables?
The solution is explained here: https://github.com/elastic/kibana/issues/2617
It's a bug that was fixed later.
I intended to implement a chat feature in my rails application. After a brief backup work I found JUGGERNAUT is the best option. By going to through http://juggernaut.rubyforge.org/
I have successfully implemented the juggernaut in my application.
Presently I'm all set to implement chat feature and after a vigorous surfing over web I couldn't get good tutorial to implement it but I found the some part of implementation at http://www.golygon.com/2010/12/private-chat-room-in-ruby-on-rails-3-0/. I decided to follow it but initially to implement the tutorial we need to have redis server and node.js in our system. I installed both in my environment.
But I'm facing the following problem as follows:
If I try
redis-server, I'm getting the following error
[11440] 08 Aug 10:08:16 # Warning: no config file specified, using the default config. In order to specify a config file use 'redis-server /path/to/redis.conf'
[11440] 08 Aug 10:08:16 # Opening port: bind: Address already in use
and as per the tutorial
if I try
sudo node server.js, I'm getting the following error
[sudo] password for re5:
node.js:63
throw e;
^
Error: ENOENT, No such file or directory '/home/re5/Documents/task17/server.js'
at Object.openSync (fs:153:18)
at Object.readFileSync (fs:94:15)
at Module._loadScriptSync (node.js:468:39)
at Module.loadSync (node.js:338:12)
at Object.runMain (node.js:522:24)
at Array.<anonymous> (node.js:756:12)
at EventEmitter._tickCallback (node.js:55:22)
at node.js:773:9
As I don't know much about the redis and node I'm unable to figure out what was the problem regarding to this errors.
I'm stuck and couldn't go further as I'm not sure whether this two are configured perfectly or not.
currently I'm using rails 3.0.7 and ruby 1.8.7
Can any one help me out.
Well your first error is quite simple to understand.
[11440] 08 Aug 10:08:16 # Opening port: bind: Address already in use
This means that there is aready a server bound to that port and using it as a server, this can happen if you have other applications/servers running or if you try to have mutiple instances of the server run at one time. To fix this you need to stop the process and then start it back up again. You can usually do this by closing all of your terminal windows or using your operating systems process manager to terminate the process, if those methods dont work for you try shutting your computer down and starting it back up. If you are still unable to start the Redis server after this then there are some more steps we can take.
The next error is due to node.js not being able to find a file that it needs. Reinstalling node.js should fix this problem for you.
Let me know if this fixes your problem or if you need more help.