I'm trying to install Heroku / HHVM / WordPress on a Debian 6 64 bits VPS to test this kind of setup for my blog (Nginx + MySQL + HP-FPM + Varnish + WordPress on another Debian 6 64 bits VPS) following the recent and promising guide done by Xiao Yu and available on GitHub.
I'm absolutelly new to Heroku/Ruby and I'm affraid I'm quite lost when something not expected is happening. The installation guide seemed to be straightforward, but it isn't clear which packages do I need to install first (PHP-FPM? Nginx? Or does this script install those by itself?) and I'm stuck on this step:
git push heroku production:master
When I execute that, I get this:
Initializing repository, done.
Counting objects: 344, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (162/162), done.
Writing objects: 100% (344/344), 72.73 KiB, done.
Total 344 (delta 139), reused 342 (delta 139)
-----> PHP app detected
! ERROR: Could not resolve composer.lock requirement for HHVM 3.1.0,
please adjust the version selector. The following runtimes are available:
hhvm-3.2.0 php-5.5.11 php-5.5.12 php-5.5.13 php-5.5.14 php-5.5.15
php-5.6.0RC4
! Push rejected, failed to compile PHP app
To git#heroku.com:xxxxxx-fortress-xxxx.git
! [remote rejected] production -> master (pre-receive hook declined)
error: failed to push some refs to 'git#heroku.com:xxxxxxx-fortress-xxxx.git'
I've tried to take a look at composer.json, edit it and include a
"php": "~5.5.11",
line on the require section, but that doesn't work... unless I have to do something before (update composer.lock? How?), which I'm not sure about.
What am I doing wrong?
Thanks!
HHVM 3.1.0 is not available (anymore), as the error message points out. You would however have to update composer.lock too.
Your best bet is to just update from the template; it's been fixed there: https://github.com/xyu/heroku-wp/commit/2a0ea2097597f72c401a63c070a14ec5031ffc9d
Related
I have tried few approaches:
1)
-I downloaded Sense from https://github.com/bleskes/sense, unzipped and pasted it in kibana-5.3.0-amd64/usr/share/kibana/plugins
-I started kibana and then I got "[warning] Plugin "Sense" was disabled because it expected Kibana version "2.0.0-snapshot", and found "5.3.0"
demetrio#nodejs ~/Servers/DBs/elasticsearch-5.3.0/bin $ cd /home/demetrio/Servers/DBs/kibana-5.3.0-amd64/usr/share/kibana/bin
demetrio#nodejs ~/Servers/DBs/kibana-5.3.0-amd64/usr/share/kibana/bin $ ./kibana
undefined accessed the autoload lists which are no longer available via the Plugin API.Use the `ui/autoload/*` modules instead.
undefined accessed the autoload lists which are no longer available via the Plugin API.Use the `ui/autoload/*` modules instead.
log [20:25:48.403] [warning] Plugin "Sense" was disabled because it expected Kibana version "2.0.0-snapshot", and found "5.3.0".
log [20:25:49.123] [info][status][plugin:kibana#5.3.0] Status changed from uninitialized to green - Ready
log [20:25:49.279] [info][status][plugin:elasticsearch#5.3.0] Status changed from uninitialized to yellow - Waiting for Elasticsearch
log [20:25:49.326] [info][status][plugin:console#5.3.0] Status changed from uninitialized to green - Ready
log [20:25:49.842] [info][status][plugin:timelion#5.3.0] Status changed from uninitialized to green - Ready
log [20:25:49.873] [info][listening] Server running at http://localhost:5601
log [20:25:49.875] [info][status][ui settings] Status changed from uninitialized to yellow - Elasticsearch plugin is yellow
log [20:25:50.041] [info][status][plugin:elasticsearch#5.3.0] Status changed from yellow to green - Kibana index ready
log [20:25:50.043] [info][status][ui settings] Status changed from yellow to green - Ready
2)
I tried installed, as suggested in https://github.com/bleskes/sense by following
demetrio#nodejs ~/Servers/DBs/kibana-5.3.0-amd64/usr/share/kibana/bin $ ./kibana plugin --install elastic/sense
ERROR unknown command plugin
3)
I tried to install
demetrio#nodejs ~/Servers/DBs/kibana-5.3.0-amd64/usr/share/kibana/bin $ ./kibana-plugin install elastic/sense
Attempting to transfer from elastic/sense
Attempting to transfer from https://artifacts.elastic.co/downloads/kibana-plugins/elastic/sense/elastic/sense-5.3.0.zip
Error: Client request error: connect ETIMEDOUT 107.21.249.70:443
Plugin installation was unsuccessful due to error "Client request error: connect ETIMEDOUT 107.21.249.70:443"
P.S. I checked my Debian proxy configuration and it is correct. Should I add my proxy configs in some specific Kibana file?
4)
I tried installed it from Google Chrome Store but it seems that such plugin is no mode maintained after version 2 and ELK is currently in 5.3
5)
I installed X-Pack (https://www.elastic.co/downloads/x-pack) but, as far as I noted until now, the only significant different was an user creation for each of ELK. I was locking for some thing like described here https://github.com/bleskes/sense
Handy API suggestions
Format validation
Scope collapsing
Auto formatting
Submit multiple requests at once
Copy and Paste cURL commands
To sum up, I am locking for some tool that could make a bit easier for a dummy like to make queries and interact with ELK. I saw few pictures that drove to conclusion that Sense is a good tool for that but I couldn't make it work.
Sense is now included in Kibana. Start Kibana (default port 5601) and look at DevTools. X-Pack is actually an expansion for monitoring, alerting and security purposes. kibana console doc
So for you it would be best to start exploring elasticsearch by using kibana devtools.
I get the following error when importing an SVN repository to git with svn2git:
fatal: EOF in data (285 bytes remaining)
Does anyone know what this error means?
This is caused by a segmentation fault, there is a branch/tag/ in your repository that is causing it to core.
To get the core files you will need to enable cores:
Uncomment this line in /etc/security/limits.conf
soft core unlimited
Run svn2git, it may take up to 2 hours to get the segmentation fault. Install gdb:
yum install gdb
Analyse the core:
gdb svn2git/svn-all-fast-export core.NNNN
Get a back trace, type:
bt
You should see the branch/tag which caused problems in the back trace. Exclude the branch from processing by updating your ruleset:
match /branches/broken_branch_name
end match
See issue opened with owner of svn2git here:
https://github.com/svn-all-fast-export/svn2git/issues/26
Or even easier, pstack <pid of svn2git> and you will see where it is stuck, then Ctrl + C, add the dud branch to your rule set and start svn2git again.
Issue description:
Install package on CentOS7 with below command:
yum install <package_name>
error:
# yum install httpd
Loaded plugins: fastestmirror
http://centos-distro.1gservers.com/7.2.1511/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 403 - Forbidden
Trying other mirror.
To address this issue, please refer to the below knowledge base article
https://access.redhat.com/solutions/69319
If above article doesn't help to resolve this issue, please create a bug on https://bugs.centos.org/
Other info
>* I can be sure I did not have a proxy setting in /etc/yum.conf.
>* The firewall is closed.
>* I already try yum clean all
Something may relate
I have added the following two to config in /etc/yum.conf
timeout=9999
minrate=0
I added them because sometimes I will hit too slow or timeout error. If I remove this two from config, the error will be replaced by
# yum install httpd
Loaded plugins: fastestmirror
http://centos-distro.1gservers.com/7.2.1511/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://centos-distro.1gservers.com/7.2.1511/os/x86_64/repodata/repomd.xml: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
The error message did give a link. But that link can only be read by RedHat support accounts. I tried googling this, but the result either none related or can not solve my problem. Stack overflow also had one post about this. But it is also not helping.
Can anyone give some advice?
I solved this issue. This is because some external, third party firewall of my lab is blocking me.
Although the root cause is not very meaningful, but the way to trouble shoot should worth mention to reference.
Trouble shooting
It said 403 for some url. So I will access that url from my compute with below command.
curl -i <url>
The output contains http header. It is 403. Then I copy the html body to some text file. Use a web Broswer to open it. I found some information like:
your orgainization firewall block you
So... it is a network problem of my lab
I am new Shogun user,besides, this is my first time to use SVN.(I think the problem is SVN not Shogun)
those are the environment what I use:
Windows 10
Shogun 4.0.0
TortoiseSVN-1.9.3.27038-x64-svn-1.9.3;
VisualSVN-5.1.3;
VisualSVN-Server-3.5.1-x64;
VS 2013
Now I am in trouble when I want to get started an simple example of Shogun(copy in Documentation) as follow:
#include <shogun/base/init.h>
using namespace shogun;
int main(int argc, char** argv)
{
init_shogun();
exit_shogun();
return 0;
}
then, I try to compile it in Vs 2013, it tell me:
1> Generating version header
3> Building Custom Rule E:/shogun/CMakeLists.txt
3> CMake does not need to re-run because E:\shogun-configure\CMakeFiles\generate.stamp is up-to-date.
3> Creating directories for 'MSIntTypes'
3> Performing download step (SVN checkout) for 'MSIntTypes'
3> svn: E170013: Unable to connect to a repository at URL ' http://msinttypes.googlecode.com/svn/trunk '
3> svn: E175012: Connection timed out
3> C:\ProgramFiles(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(170,5): error MSB6006:
"cmd.exe" has exited. code is 1.
Then, I considerd that maybe some problems with SVN, I try to checkout some respositories:
At first, I try to checkout an respositories what I create myself:'_http://burningbear:8443/!/#new_rep', it can be checkout normally.
Then I try to chekout the respository:'_http ://msinttypes.googlecode.com/svn/trunk', but the Tortoise just not responding for a long time, then it reply me that:
Command: Checkout from _http://msinttypes.googlecode.com/svn/trunk, revision HEAD, Fully recursive, Externals included
Error: Unable to connect to a repository at URL
Error: '_http://msinttypes.googlecode.com/svn/trunk'
Error: Error running context: 你的主机中的软件中止了一个已建立的连接。(what I use is Chinese,it means "the software in your host stop an connected connection")
In China, We can not access googlecode unless we use VPN, so I change the server, to enable Proxy Server, the following is my setting:
Server address: 127.0.0.1
Port: 8087
Then I try to checkout again as:
When I check out _http://msinttypes.googlecode.com/svn/trunk
Checkout from _http://msinttypes.googlecode.com/svn/trunk, revision HEAD, Fully recursive, Externals included
Unable to connect to a repository at URL'_http://msinttypes.googlecode.com/svn/trunk'
The HTTP method 'OPTIONS' is not allowed on '/svn/trunk'
When I update the repositories what I have checkout before(URL is :_http://burningbear:8443/!/#new_rep). It move slowly, I spend about half hour, SVN tell me: "2 kBytes transferred in 20 minutes and 2 seconds"
Command: Update
Updating: E:\test2
Error: Unable to connect to a repository at URL 'https://burningbear:8443/svn/new_rep'
Error: Connection timed out
Completed!:
Now, I don't know what's the problem. It take me several days and I still can not solve it. Please help me! Thank you in advanced!
(I can not post more than 2 links now, so all of URL above I add an '_' mark before 'http')
Currently there's no way to compile natively shogun on Windows unfortunately. Although your problem seems to be unrelated, and it fails with svn, which is weird because the official repo of the shogun is using git: http://github.com/shogun-toolbox/shogun/
worked on the weekend on the native Windows support of shogun, you can find it in the feature/windows branch of the official repository: https://github.com/shogun-toolbox/shogun/tree/feature/windows
UPDATE: the feature branch has been merged into develop branch. from now on shogun can be compiled on windows natively.
Google Code is not available anymore: http://msinttypes.googlecode.com/svn/trunk. That's why the tool fails to access googlecode.com.
Today's (1 Mar 2016) OpenSSL release has caused the following error when running Plone/Zope
.buildout/eggs/ZODB3-3.10.5-py2.7-linux-x86_64.egg/persistent/cPersistence.so: undefined symbol: SSLv2_method
It's hard to see what's going on since it's a binary file. I also tried updating to ZODB3 3.11.0 which yields the following traceback
.buildout/eggs/ZConfig-2.9.0-py2.7.egg/ZConfig/loader.py", line 217, in schemaComponentSource
package=package)
ZConfig.SchemaResourceError: could not load package ZServer:
.buildout/eggs/zope.security-3.7.4-py2.7-linux-x86_64.egg/zope/security/_proxy.so: undefined symbol: SSLv2_method
Package name: 'ZServer'
File name: 'component.xml'
Package path: None
Is there any workaround for this other than reverting OpenSSL?
zope security is a compiled egg, like all the ones ending with -py2.7-linux-x86_64.egg.
As the traceback says, it cannot find anymore a symbol.
Probably you have to recompile it with the new openssl-dev.
I would try (on a development server first):
backup your compiled egg (mkdir eggs-backup && mv `eggs/zope.security-3.7.4-py2.7-linux-x86_64.egg eggs-backup/)
rerun buildout
This will recompile your missing egg.
Hopefully it works and hopefully it is the only one linked to that library.
Anyway, dependending on the way you patched openssl you may have a lot of other issues (I am thinking about Python, urllib*, curl, wget, ...)
OpenSSL 1.0.2g by default doesn't build with SSLv2 (because of the recent DROWN attack). You may need to manually build it without OPENSSL_NO_SSL2 flag.
(but in fact you shouldn't do this if you're doing some server-related stuff, there is a serious security reason because of which it was disabled, see https://drownattack.com)
I was able to resolve this by upgrading python to 2.7.10+, and then upgrading Pillow and lxml.