For some strange reason ESXi 6.5 root password isn't working on a new installation. I even tried removing the password by modifying shadow file (following this guide) and still it doesn't allow me to login with a blank password.
Any idea what could be wrong with a new installation? I'm trying to run ESXi using Qemu.
I've set the password as password
But during login it says invalid password.
Figured it out.
The problem was with Qemu Emulator. I was testing using old version of qemu (3.x) but I can't login when I use 3.x version of Qemu. I then started the ESXi using 7.x version of qemu and I was able to login.
Related
On my server I am using Chromedp (a Go package) that runs a headless version of chrome to generate PDFs for me.
When I run this process on my windows machine it works great. Then when I try to run it on my Amazon Linux AMI server I always get the error message "context cancelled"
I asked on their github page if that was an issue with something I was doing and I was told that it might be happening if the browser crashes or fails to start.
How can I verify that my version of chrome is working through the command line?
I followed this guide when I was installing chrome.
I'm a noob trying to learn Django for the first time, I created a project in a virtualenv on Windows 10. It worked well in the beginning where I was able to login to the admin section after running '''python manage.py runserver'''
But now when I run the same command I'm able to see the Django landing page but as soon as I try to hit http://localhost:8000/admin/ or http://127.0.0.1:8000/admin the server automatically disconnects and I get the "This site can’t be reached" error on Chrome.
I tried changing the port number by running python manage.py runserver 0.0.0.0:8001 but it didn't work. I tried to check if the port (8000) is currently in use by running the cmd (as an admin) netstat -a -b but couldn't find any issues.
The server just quits without any error message
Edit: Currently using Python 3.7.0 and django-3.0.1
There's a ticket about this issue: https://code.djangoproject.com/ticket/31067.
This seems to be a bug in Python 3.7.0, and appears to be fixed in Python 3.7.1. It's still unknown what the exact trigger is for this bug.
Since Django officially only supports the latest patch release of a Python series, this won't be fixed in Django. You can either upgrade your Python version to the latest patch release of 3.7, or downgrade Django to 2.2.
It's a Django 3.0 issue as I've seen. There are so many issues on GitHub, regarding this error.
You may try downgrading to Django 2.* versions for now. Version 2.1/2.2 works fine.
I have a fossil repository on chiselapp.com. I have used it for several years on a variety of machines.
I have recently cloned the repo onto a new machine running Windows 10 and fossil 2.8 [f8d7f76bfd]. When I try to push changes to chiselapp, I get the error
missing or incorrect password for user "username"
I've configured the remote url as
https://<username>:<password>#chiselapp.com/user/<chiselapp-user>/repository/<repo-name>
which fossil reports as
https://<username>#chiselapp.com/user/<chiselapp-user>/repository/<repo-name>
without the password. I assume this is a security feature of fossil.
I'm confident that I've set the correct password for <username> since I can use that password in chiselapp once I've logged in as <chiselapp-user>.
After
fossil push
as well as the error message locally, there is no entry in the access log on chiselapp.
Please can someone tell me where I'm going wrong and how to set myself up to be able to push changes. Apart from the username I can't see any configuration difference between a Windows 7 machine from which I can push changes and the Windows 10 machine from which I can't. Both usernames are set up with bs capabilities on chiselapp.
Thanks for any help.
Update (10-Aug-2019)
I'm in the middle of building a new laptop running Linux Mint. I've downloaded fossil (now version 2.9) and wasn't suprised that it was a bit of a struggle to be able to push to chiselapp, but I managed it eventually.
I've put fossil 2.9 onto the Windows 10 machine and have configured the remote url exactly the same as on the mint machine; I'm confident of this because I can see both command-lines. I still get the error when I try to push from the Windows machine.
(A slight difference between mint and Windows 10 operation is that on Mint I see a prompt
remember password (Y/n)?
which doesn't appear on Windows. Is this a porting-related bug?)
I asked about this on the forum over at the fossil website.
It turned out that my problems were caused by using the Windows version of fossil from a cygwin window rather than the version that comes as part of the cygwin distribution.
Now that I have installed the later version of fossil and am using that from the cygwin command line, everything is working beautifully.
Goal:
Run cfquery of remote server on local Coldfusion install.
Problem/Symptoms:
The cfquery parameters are printing onto the screen, instead of running query on remote.Example of cfquery parameter printout on screen
Facts:
Running Mac OS X Mojave (10.14.3).
Coldfusion is installed. I can access the CF Admin panel at http://localhost:8500/CFIDE/administrator/index.cfm
Data Source is installed in Coldfusion Admin and status is "OK"
Using Mamp Pro 5.3. It's running -- can start and stop Apache.
Apache is running on port 80
Updated ODBC Actual SQL Server drivers (Version 4.2.0 from ActualTech). Tested connection to server with driver and it is working.
Remote database is using port 1433
I'm sure there are more questions to answer, but hopefully that's a decent start. What am I doing wrong?
Update: 3/17/2019
Feeling stuck here. I've uninstalled and reinstalled CF2018 and MAMP Pro. I've used the wsconfig applet for Adobe Coldfusion (ACF) as described by Brian Lang and I've also tried the manual approach as described by Adobe.
Update: 4/19/2019
I may have figured this out, now that there is a release of Mac OS 10.14.4. Going to test it on another computer to confirm that the process works and that I have all the steps documented, then will share answers.
The solution to this problem had to do with a conflict with Mac OS X and Coldfusion/Apache. Because Mac OS X 10.14.4 fixed the "mod_jk" file that was conflicting with Apache, Coldfusion 2018 can now run on Mac OS X.
In order to solve the problem, I needed to:
upgrade Mac OS X to 10.14.4
stop all other servers
install Coldfusion 2018
set up Coldfusion Apache Connector
set up local virtual host
I confirmed that it worked on another computer, and have documented detailed instructions in this post: https://www.steckinsights.com/configuring-coldfusion-2018-with-apache-on-mac-os-x-mojave/
Fair warning: I think that the mod_jk issue in Mac OS 10.14.3 and prior was the issue, but there were so many different aspects I tested in the process, that there may be unique issues related to your particular computer's configuration. I hope hope this helps anyone out there having issues.
Previously installed vtiger 6.5 and had active directory authentication working as per Vtiger 6 CRM AD
Clean Installed Vtiger CRM 7.1 and followed same procedure again for AD, user authenticates ok but it just loops back to the login page again.
Anyone experience this with 7.1?
Have checked config.php and confirm "$AUTHCFG['authType'] = 'AD';" is there.
Have also run the test ldap script and user also authenticates ok.
You seem to be doing everything right but I have found your not the only one with this issue, but if you take a copy of your 6.5 version and migrate to 7.1 using vtiger new files
If you are upgrading from 6.5 to 7.1, you will need to run this process twice. First to upgrade vtiger 6.5 to 7.0 and after that repeat the process to upgrade vtiger 7.0 to 7.1
Download the migration path from the SourceForge site. Patch 6.5 to 7 or Patch 7.0 to 7.1
Unzip patch.zip into Vtiger CRM Folder. A file called vtiger7.zip and migrate folder will be unpacked.
Through browser open /migrate path http://yourdomain.info/vtigercrm/migrate
Someone has successfully compete what you are trying to achieve.
https://discussions.vtiger.com/discussion/188023/vtiger-7-1-active-directory