This is really REALLY damn frustrating. For some reason Bitnami WAMP Stack keeps on FAILING to install in a deeper directory D:\***\***\***\***\***\wampstack. It ONLY works when I'm installing in the root (one folder in D:\Bitnami\wampstack). My set up NEEDS to have the stack server installed deeper down for organization's sake, but it won't work. It keeps failing.
I then tried installing it in the root directory, then tried moving the whole folder (since IT IS supposed to be self-contained.) into the proper directory (deeper down), and then changing the ImagePath of the wampserverApache and wampserverMySQL to reflect that of the new location. IT STILL WON'T START.
I keep getting this error:
> Starting all servers... Starting MySQL Database... Exit code: 1
> Stdout:
>
> Stderr: Unknown error starting mysql Starting Apache Web Server...
> Exit code: 1 Stdout:
>
> Stderr: Unknown error starting apache
Any idea on how to fix this? Or am I just doing something extremely wrong. Please help. My OCD is killing me spent a good 3 hours on this stupid issue. I just don't understand why the installer won't let me just install in a deeper directory. It lets me change the directory during installation but it doesn't ever work. Bitnami really should fix this if they're letting you change the directory in which to install, or at least limit the choices so that the user doesn't get stuck needlessly trying to figure out the problem with the installation.
Bitnami developer here.
The problem you're facing must be related to the length of your path. This is a NTFS limitation, this is a related case:
Maximum filename length in NTFS (Windows XP and Windows Vista)?
Could you check if your path is longer than 255 characters?
Also spaces in directory names can be an issue, as all this software is ported from unix where spaces in directory names require the use of quotes around paths that contain spaces. So either check the config and put quotes around your paths that contain spaces like "folder 1/folder 2" or remove/replace the spaces in the paths.
Related
I just update my google cloud SDK on windows 10 (gcloud components update).
After the update the gcloud command stop working.
All I get is (for example : gcloud -h):
PATH\lib\gcloud.py" -h" was unexpected at this time.
I try to re-install but it didn't help:(
As noted in the other answers, this is a bug with the 274.0.0 version of gcloud. Another report of this issue actually identifies where the bug is and offers this fix:
If you are stuck and need an immediate solution, here's a workaround that will move you forward, but you should reinstall the Cloud SDK from scratch when a fix is ready.
Open C:\Program Files (x86)\Google\Cloud SDK\google-cloud-sdk-bin\gcloud.cmd in your editor
Near line 170, change ) ELSE ( to be just )
Remove the ) on the last line in the file.
That should get you working in the short term (albeit with an extraneous error message every time you run a command). After getting it working you can revert to version 273.0.0 (so that you stop getting the error message and aren't using a modified version) using:
gcloud components update --version=273.0.0
This is being tracked in the public bug https://issuetracker.google.com/issues/146458519
We have a patch for two files that are causing these problems. These apply in two cases (both on Windows):
1. A new install fails, or
2. You are unable to run gcloud after performing a components update.
For case # 1, please download the attached file install.bat, and copy it to the location where you have attempted to install gcloud, e.g. C:\Program Files (x86)\Google\Cloud SDK\google-cloud-sdk. Then run it, e.g.
cd C:\Program Files (x86)\Google\Cloud SDK\google-cloud-sdk
.\install.bat
For both cases #1 and #2, download the attached file gcloud.cmd, and copy it to the bin directory under your gcloud installation, e.g.
C:\Program Files (x86)\Google\Cloud SDK\google-cloud-sdk\bin. When prompted to replace the previous copy, type Yes. This should allow you to run gcloud without being prompted to set CLOUDSDK_PYTHON.
The files are attached in the public bug tracker.
This is a known issue that is being tracked here
After hours of trying to fix it! I found how :)
uninstall google SDK
https://dl.google.com/dl/cloudsdk/channels/rapid/google-cloud-sdk.zip
https://cloud.google.com/sdk/docs/downloads-interactive#interactive_installation
This fix the bug.
After that I had new bug in pyCharm GAE:
ImportError: No module named _subprocess
I fix this with the solution here:
Error importing built-in module "_subprocess" using Google Cloud Platform's Local Development Server
Hope this helps and saves a lot of trouble for you guys :)
I solved this problem. I got the same error message.
My Env: gcloud v274.0.0, Windows 7
First, I re-installed Google SDK, and changed my path to \Google\CloudSDK\.
Second, I got this message
"\Google\CloudSDK\google-cloud-sdk\bin..\lib\gcloud.py" init" was unexpected at this time."
So I tried to use cd command to specific directory where gcloud.py is exist.
Finally, I found the path: \Google\CloudSDK\google-cloud-sdk\lib, and it works.
Hope it can help you, too.
The problem, or rather bug within the installer, is that you are using a directory that contains spaces within it. At some point of the script the space causes the command to be split up incorrectly, causing the error.
I had the same message and fixed it by re-installing the Google Cloud SDK in a directory without spaces (c:\Google\CloudSDK)
I am very Beginner to Drupal, And Currently I want to install 8.7.7 Drupal Version in My 7.2.19 Php version Xampp but During installation I got first Warning like
PHP OPCODE CACHING
Not enabled
PHP OPcode caching can improve your site's performance considerably. It is highly recommended to have OPcache installed on your server.
After that I added below code to Php.ini file
zend_extension="C:\xampp\php\ext\php_opcache.dll"
zend_extension=php_opcache.dll
Then I got other Fatal Error like,
Fatal error: Uncaught Error: Class 'Drupal\Component\Utility\OpCodeCache' not found in C:\xampp\htdocs\orange\core\install.php:37 Stack trace: #0 {main} thrown in C:\xampp\htdocs\orange\core\install.php on line 37
Can Anyone help me to solve this problem?
Not working for me
zend_extension="C:\xampp\php\ext\php_opcache.dll"
zend_extension=php_opcache.dll
opcache.enable=1
opcache.enable_cli=1
opcache.memory_consumption=256
opcache.max_accelerated_files=2000
You might have missed the enable line before the zend stuff. Also, did you restart the web server?
Try this
open a php.ini file
1 Change the ;opcache.enable=1 to opcache.enable=1
2 Add opcache dll path at the end of the file zend_extension = "C:\xampp\php\ext\php_opcache.dll"
3 Restart apache
Credits to : Windows, XAMPP, PHP 7 and opcache
Update:
Maybe it’s using another php.ini file. 1) Try this to reveal the loaded file - use example 1 in link below.
https://www.php.net/manual/en/function.php-ini-loaded-file.php
2)
Then see if opcache extensions are loaded by printing the file itself:
Put test.php somewhere in in you website with following content
<?php phpinfo();?>
So, I'm working on a robotframework test project, and the goal is to run several test suites in parallel. For this purpose, pabot was chosen as the solution. I am trying to implement it, but with little success.
My issue is: after installing Pabot (which, I might say, I did by cloning the project and running "setup.py install", instead of using pip, since the corporate proxy I'm behind has proven an obstacle I can't overcome), I created a new directory in the project tree, moved some suites there, and ran:
pabot --processes 2 --outputdir pabot_results Login*.robot
Doing so results in the following error message:
2018-10-10 10:27:30.449000 [PID:9676] [0] EXECUTING Suites.LoginAdmin
2018-10-10 10:27:30.449000 PID:400 EXECUTING Suites.LoginUser
2018-10-10 10:27:30.777000 PID:400 FAILED Suites.LoginUser
2018-10-10 10:27:30.777000 [PID:9676] [0] FAILED Suites.LoginAdmin
WARN: No output files in "pabot_results\pabot_results"
Output:
[ ERROR ] Reading XML source '' failed: invalid mode ('rb') or filename
Try --help for usage information.
Elapsed time: 0 minutes 0.578 seconds
Upon inspecting the stderr file that was generated, I have this message:
Traceback (most recent call last):
File "C:\Python27\Lib\site-packages\robotframework-3.1a2.dev1-py2.7.egg\robot\running\runner.py", line 22, in
from .context import EXECUTION_CONTEXTS
ValueError: Attempted relative import in non-package
Apparently, this has to do with something from the runner.py script, which, if I'm not mistaken, came with the installation of robotframework. Since manually modifying that script does not seem to me the optimal solution, my question is, what am I missing here? Did I forget to do anything while setting this up? Or is this an issue of compatibility between versions?
This project is using Maven as the tool to manage dependencies. The version I am running is 3.5.4. I am using a Windows 10, 64bit system; I have Python 2.7.14, and Robot Framework 3.1a2.dev1. The Pabot version is 0.44. Obviously, I added C:\Python27 and C:\Python27\Scripts to the PATH environment variable.
Edit: I am also using robotframework-maven-plugin version 1.4.0.8, if that happens to be relevant.
Edit 2: added the error messages in text format.
I believe I've come across an issue similar when setting up parallel execution on my machine. Firstly I would confirm that pabot is installed using pip show robotframework-pabot.
Then you should define the directory your results are going to using -d.
I then modified the name of the -o to Output.xml to make it easy to identify.
This is a copy of the code I use. Runs optimally with 8 processes
pabot --processes 8 -d results -o Output.xml Tests
Seems that you stumbled on a bug in the prerelease version of robot framework (3.1a2.dev1).
Please install a release version of robot framework. For example 3.0.4.
Just in case anyone happens to stumble upon this issue in the future:
Since I can't use pip, and I tried a good deal of workarounds that eventually made things more unstable, I ended up saving my project and removing everything Python-related from my system, so as to allow me to install everything from scratch. In a Windows 10, 64bit system, I used:
Python 2.7.14
wxPython 2.8.12.1, win64, unicode, for py27
setuptools 40.2.0 (to allow me to use the easy_install command)
Robot Framework 3.0.4
robotremoteserver 1.1
Selenium2Library 3.0.0
and Pabot version 0.45.
I might add that, when installing the Selenium2Library the way I described above, it eventually tries to download some things from the pip repositories - which, if you have a proxy, will cause you trouble. I solved this problem by browsing https://pypi.org/simple/selenium/, manually downloading the 2.53.6 .tar.gz file, then extracting it and running setup.py install on the command line.
PS: Ideally, though, anyone should be able to use proxy settings from the command line (--proxy http://user:password#server:port) to get pip and then use it; however, for some reason, probably related to network security configurations that I didn't want to lose time with, this didn't work in my case.
I installed php7.0.15/apache2.4.25/phpMyAdmin 4.6.5.2 via xampp, but it turns out that the extensions xsl and intl are missing (need them to run Magento2).
I'm using Windows 8.1.
Both files php_xsl.dll and php_intl.dll exist in xampp/php/ext and I tried deleting the related ";" from extension=.. from in php.ini,
re-saving the php.ini and restarting apache server;
also copied in apache/bin folder the icu*.dll files from php;
BUT no success with that: still missing with magento2 Readiness Check.
Have any advise?
I have two suggestions for you---
No.1
Are you restarting the apache as administrator as I forget to do that most of the time.
No.2
Check your environment variable path. Did you set it properly.
Hope this can help!
I install LXR in my PC to build reference of Linux source code, I follow the step of LXR manual, every thing is done, but when I open my website, the page said "Unrecoverable error, No known root for source-tree lxr", could anybody help?
I've just recently encountered the same problem after
having to reinstall everything on my server
for me, the problem was
misspelled 'host_names' parameter in lxr.conf file
the apache server wasn't able to the config through the name given in the URL
maybe you should check if the path leading up to your lxr.conf file is readable by user
'www-data'