Couldn't resolve error at 'nt! swapcontext' in Windbg - windows

OK so I ran the following command from the Windbg command prompt as follows:
lkd> uf nt! swapcontext
and got the following error:
Couldn't resolve error at 'nt! swapcontext'
I then ran the following command from the Windbg command prompt:
.reload /f /v ntoskrnl.exe
and got the following output:
lkd> .reload /f /v ntoskrnl.exe
AddImage: \SystemRoot\system32\ntoskrnl.exe
DllBase = fffff802`3580a000
Size = 0077a000
Checksum = 007122c1
TimeDateStamp = 623d2df2
SYMSRV: BYINDEX: 0x10
C:\symbolcache*https://msdl.microsoft.com/download/symbols
ntkrnlmp.pdb
610455A6355B4DEFB6BAA86D9F7967EE1
SYMSRV: UNC: C:\symbolcache\ntkrnlmp.pdb\610455A6355B4DEFB6BAA86D9F7967EE1\ntkrnlmp.pdb - path not found
SYMSRV: UNC: C:\symbolcache\ntkrnlmp.pdb\610455A6355B4DEFB6BAA86D9F7967EE1\ntkrnlmp.pd_ - path not found
SYMSRV: UNC: C:\symbolcache\ntkrnlmp.pdb\610455A6355B4DEFB6BAA86D9F7967EE1\file.ptr - path not found
SYMSRV: HTTPGET: /download/symbols/ntkrnlmp.pdb/610455A6355B4DEFB6BAA86D9F7967EE1/ntkrnlmp.pdb
SYMSRV: HttpQueryInfo: 80190194 - HTTP_STATUS_NOT_FOUND
SYMSRV: HTTPGET: /download/symbols/ntkrnlmp.pdb/610455A6355B4DEFB6BAA86D9F7967EE1/ntkrnlmp.pd_
SYMSRV: HttpQueryInfo: 80190194 - HTTP_STATUS_NOT_FOUND
SYMSRV: HTTPGET: /download/symbols/ntkrnlmp.pdb/610455A6355B4DEFB6BAA86D9F7967EE1/file.ptr
SYMSRV: HttpQueryInfo: 80190194 - HTTP_STATUS_NOT_FOUND
SYMSRV: RESULT: 0x80190194
DBGHELP: ntkrnlmp.pdb - file not found
DBGHELP: nt - export symbols
My _NT_SYMBOL_PATH environment variable is set to the following:
c:\symbols;cachec:\symbolcache;\server\symbols;SRVc:\symbols*http://msdl.microsoft.com/download/symbols
Do the errors indicate that there is a problem with the Microsoft Symbol Server i.e. symbol file not found on the server or could it be that there is a configuration issue on my end ? I'm running Visual Studio 2019 and Windbg on Windows 8.1.

Related

Laravel on AWS with SSL - 404 Not Found errors

I have a laravel project I am trying to run on AWS Elasticbeanstalk - I uploaded the project and worked 100% using HTTP, the client decided they wanted SSL , when I upload the exact same source code, my landing page works perfectly (https://sitename/), however any other page such as https://sitename/login will not work at all and I receive a 404 Not Found errors message.
The output I have is as follows (I zero'ed out the ip address except the last section to give it context):
2022/05/25 03:51:46 [error] 7872#7872: *21072 open() "/var/www/html/public/login" failed (2: No such file or directory), client: 000.00.00.164, server: , request: "GET /login HTTP/1.1", host: "00.000.000.113"
2022/05/25 03:57:03 [error] 7871#7871: *21210 open() "/var/www/html/public/_debugbar/assets/javascript" failed (2: No such file or directory), client: 000.00.00.164, server: , request: "GET /_debugbar/assets/javascript?v=1644364352 HTTP/1.1", host: "portal.sitename", referrer: "https://portal.sitename/"
2022/05/25 03:57:03 [error] 7872#7872: *21209 open() "/var/www/html/public/_debugbar/assets/stylesheets" failed (2: No such file or directory), client: 000.00.00.164, server: , request: "GET /_debugbar/assets/stylesheets?v=1644364352&theme=auto HTTP/1.1", host: "portal.sitename", referrer: "https://portal.sitename/"
2022/05/25 04:01:26 [error] 7872#7872: *21313 open() "/var/www/html/public/ReportServer" failed (2: No such file or directory), client: 000.00.00.193, server: , request: "GET /ReportServer HTTP/1.1", host: "13.244.47.136"
2022/05/25 04:01:39 [error] 7872#7872: *21320 open() "/var/www/html/public/ReportServer" failed (2: No such file or directory), client: 000.00.00.164, server: , request: "GET /ReportServer HTTP/1.1", host: "00.000.000.113"
2022/05/25 04:08:15 [error] 7872#7872: *21477 open() "/var/www/html/public/login" failed (2: No such file or directory), client: 000.00.00.193, server: , request: "POST /login HTTP/1.1", host: "portal.sitename", referrer: "https://portal.sitename/"
This is happening because your server is not accepting query string in url. For solving this you should add another folder called .platform and follow the text inside laravel.conf file like below. This will be fixed
Be sure you are using nginx as server from elastic benstalk configuration
.platform configuration
laravel.conf file
location / {
try_files $uri $uri/ /index.php?$query_string;
gzip_static on;
}
There's documentation available for laravel in combination with beanstalk.
Your issue is caused by the webserver searching for files in the wrong directory. Did you choose PHP as platform? And do you have set the Document Root to /public?
Thanks to all for assisting , for anyone following this is what I did to resolve:
cd /etc/nginx/conf.d/elasticbeanstalk
nano laravel.conf
added the following code:
location / {
try_files $uri $uri/ /index.php?$query_string;
}

How to configure Xdebug with Laradock and PhpStorm

I'm trying to configure Xdebug with PhpStorm and Laradock.
I started with this:
https://laradock.io/documentation/#install-xdebug
I can see that Xdebug is working:
php-fpm/xdebug status
with Xdebug v2.9.6, Copyright (c) 2002-2020, by Derick Rethans
This is my PhpStorm config:
I added a breakpoint and the debugger is not stopping.
Can anyone see what I am doing wrong?
My project is in /code/test which is /var/www on the server.
Laradock is in /code/laradock
UPDATE:
Xdebug log shows:
[6] Log opened at 2020-07-10 10:44:55
[6] I: Connecting to configured address/port: host.docker.internal:9000.
[6] E: Time-out connecting to client (Waited: 200 ms). :-(
[6] Log closed at 2020-07-10 10:44:55
Update:
changed ini to this (and port in IDE):
xdebug.remote_host=192.168.68.101
xdebug.remote_connect_back=0
xdebug.remote_port=9001
[6] Log opened at 2020-07-10 12:11:03
[6] I: Connecting to configured address/port: 192.168.68.101:9001.
[6] E: Time-out connecting to client (Waited: 200 ms). :-(
[6] Log closed at 2020-07-10 12:11:04
I got this working, I had to do a couple of things:
Turned my firewall off.
changed my config:
xdebug.remote_host="172.17.0.1" # this is listed under docker0 using ifconfig
xdebug.remote_connect_back=0
xdebug.remote_port=9000
xdebug.idekey=PHPSTORM

ddev Xdebug and step debugging not working with PhpStorm

I'm new to ddev, but not new to Ansible, Vagrant, etc, or setting up Xdebug, and I can't for the life of me get step debugging to work with PhpStorm and ddev. I've tried changing ports and did all the steps in this thread How do I get xdebug/step-debugging working with ddev? to no avail. What am I missing?
Here are my settings:
APIVersion: v1.13.0
name: ee-dev-clean
type: php
docroot: ""
php_version: "7.3"
webserver_type: nginx-fpm
router_http_port: "80"
router_https_port: "443"
xdebug_enabled: true
additional_hostnames: []
additional_fqdns: []
nfs_mount_enabled: false
provider: default
use_dns_when_possible: true
timezone: ""
I'm setting my own 20-xdebug.ini file which is 100% accepted and showing correct values when I run phpinfo(). These are basically the same settings that do work in other Ansible/Vagrant based machines that I have running locally (all of them have been suspended while testing ddev).
[XDebug]
zend_extension=xdebug.so
; zend_extension="/usr/lib/php/20190902/xdebug.so"
xdebug.remote_host=host.docker.internal
xdebug.remote_enable=1
xdebug.remote_connect_back=1
xdebug.show_exception_trace=0
; xdebug.remote_port=11011
xdebug.idekey=PHPSTORM
xdebug.remote_log="/var/log/xdebug.log"
The xdebug.log file has the following output after making a request and attempting to pick up a break point. I also have "stop at first line" enabled.
[1038] I: Remote address found, connecting to 172.18.0.1:9000.
[1037] I: Remote address found, connecting to 172.18.0.1:9000.
[1037] W: Creating socket for '172.18.0.1:9000', poll success, but error: Operation now in progress (29).
[1038] W: Creating socket for '172.18.0.1:9000', poll success, but error: Operation now in progress (29).
[1037] E: Could not connect to client. :-(
[1037] Log closed at 2020-02-19 19:56:05
[1038] E: Could not connect to client. :-(
[1038] Log closed at 2020-02-19 19:56:05
[1057] Log opened at 2020-02-19 19:56:50
[1057] I: Checking remote connect back address.
[1057] I: Checking header 'HTTP_X_FORWARDED_FOR'.
[1057] I: Remote address found, connecting to 172.18.0.1:9000.
[1057] W: Creating socket for '172.18.0.1:9000', poll success, but error: Operation now in progress (29).
[1057] E: Could not connect to client. :-(
[1057] Log closed at 2020-02-19 19:56:50
[1037] Log opened at 2020-02-19 19:56:51
[1037] I: Checking remote connect back address.
[1037] I: Checking header 'HTTP_X_FORWARDED_FOR'.
[1037] I: Remote address found, connecting to 172.18.0.1:9000.
[1038] Log opened at 2020-02-19 19:56:51
[1038] I: Checking remote connect back address.
[1038] I: Checking header 'HTTP_X_FORWARDED_FOR'.
[1038] I: Remote address found, connecting to 172.18.0.1:9000.
[1037] W: Creating socket for '172.18.0.1:9000', poll success, but error: Operation now in progress (29).
[1038] W: Creating socket for '172.18.0.1:9000', poll success, but error: Operation now in progress (29).
[1037] E: Could not connect to client. :-(
[1037] Log closed at 2020-02-19 19:56:51
[1038] E: Could not connect to client. :-(
[1038] Log closed at 2020-02-19 19:56:51
Ok, it was the port. I had to set it up to use port 11011 instead of 9000. Removed the 20-xdebug.ini entire override and added an xdebug-port.ini file with just the following:
[XDebug]
xdebug.remote_port=11011
Then changed the project settings in PhpStorm:
Also added the following server settings (though PhpStorm figured this out for me when it saw the incoming connection:

How do I fix php7.1-fpm.sock failure on Laravel

I am trying to solve my white screen problem. Currently, I'm unable to login to one of my staging servers. I'm running Laravel 5.2 / php 7.1-fpm. After doing a repository update(via Forge), I hit the white screen view.
Based on my domain error log, I think that fixing the php7.1-fpm.sock failure will solve my white screen error.
I've tried just about every suggestion from various forums; I've tried suggestions from several similar related stack-overflow threads.
I still haven't found a solution. Can anyone offer suggestions?
Below is the error.log contents:
2018/08/12 21:16:09 [crit] 949#949: *28 SSL_do_handshake() failed
(SSL: error:1417D102:SSL routines:tls_process_client_hello:unsupported
protocol) while SSL handshaking, client: 23.27.154.95, server:
0.0.0.0:443
2018/08/13 00:43:46 [crit] 949#949: *47 SSL_do_handshake() failed (SSL: error:1417D102:SSL
routines:tls_process_client_hello:unsupported protocol) while SSL
handshaking, client: 220.181.132.198, server: 0.0.0.0:443
2018/08/13 00:43:46 [crit] 949#949: *48 SSL_do_handshake() failed (SSL:
error:1417D18C:SSL routines:tls_process_client_hello:version too low)
while SSL handshaking, client: 220.181.132.198, server: 0.0.0.0:443
2018/08/13 00:43:47 [crit] 949#949: *49 SSL_do_handshake() failed
(SSL: error:1417D102:SSL routines:tls_process_client_hello:unsupported
protocol) while SSL handshaking, client: 220.181.132.198, server:
0.0.0.0:443
Below is my site's error log contents:
2018/08/11 17:48:31 [crit] 934#934: *1 connect() to
unix:/var/run/php/php7.1-fpm.sock failed (2: No such file or
directory) while connecting to upstream, client: 73.106.222.129,
server: blabs.goteachersintouch.com, request: "GET / HTTP/2.0",
upstream: "fastcgi://unix:/var/run/php/php7.1-fpm.sock:", host:
"blabs.goteachersintouch.com"
2018/08/11 17:48:35 [crit] 1266#1266: *1 connect() to unix:/var/run/php/php7.1-fpm.sock failed (2: No such file
or directory) while connecting to upstream, client: 73.106.222.129,
server: blabs.goteachersintouch.com, request: "GET /img/body-bg.png
HTTP/2.0", upstream: "fastcgi://unix:/var/run/php/php7.1-fpm.sock:",
host: "blabs.goteachersintouch.com", referrer:
"https://blabs.goteachersintouch.com/build/css/app-5aaeb8644f.css"
Before I did the Repository Uninstall with Laravel Forge, my build was working fine. Apparently setting my server to it's original PHP state is not in alignment with some configuration (there's something I'm missing, I just can't see it).
My codebase is still running on Laravel 5.2 library. But even still, can anyone offer suggestions to fix this white screen issue.
I have tried the permissions adjustments--that hasn't worked.
Thank you!
Turns out I was missing a bower file. The file was angular-sanitize#1.6.1
I ran:"bower install angular-sanitize#1.6.1" and was up and running again.

Starting Realm Object server on AWS stalls

I've been trying to use Realm Object Server deployed on an Amazon ec2 instance, using the basic Amazon Ubuntu AMI (since the Realm AMI has ROS v.1.8.3).
To use the latest ROS (v2.x) I followed Realm's instructions to use curl -s https://raw.githubusercontent.com/realm/realm-object-server/master/install.sh | bash which appears to execute successfully. I follow that script's instructions to load nvm and use its latest version.
Then I run ros start. Here's what I get:
info: Loaded feature token capabilities=[Sync], expires=Wed Apr 19 2017 14:15:29 GMT+0000 (UTC)
info: Realm Object Server version 2.0.18 is starting
info: [sync] Realm sync server started ([realm-core-4.0.3], [realm-sync-2.1.4])
info: [sync] Directory holding persistent state: /home/ubuntu/data/sync/user_data
info: [sync] Operating mode: master_with_no_slave
info: [sync] Log level: info
info: [sync] Download log compaction is enabled
info: [sync] Max download size: 131072 bytes
info: [sync] Listening on 127.0.0.1:40134 (sync protocol version 22)
info: [http] 127.0.0.1 - GET /realms/files/%2F__wildcardpermissions HTTP/1.1 200 55 - 56.996 ms
info: [http] 127.0.0.1 - GET /realms/files/%2F__password HTTP/1.1 200 44 - 53.009 ms
info: [http] 127.0.0.1 - GET /realms/files/%2F__perm HTTP/1.1 200 40 - 9.402 ms
info: Autocreated admin user: realm-admin
info: Realm Object Server has started and is listening on http://0.0.0.0:9080
info: [http] 127.0.0.1 - GET /realms/files/%2F__admin HTTP/1.1 200 41 - 4.187 ms
info: [http] 127.0.0.1 - GET /realms/files/%2F__admin HTTP/1.1 200 41 - 29.902 ms
And then...nothing. It doesn't even get me back to my ubuntu#ip-XXX-XX-XX-XX: prompt. (It's possible that this is exactly what you'd expect but I'm pretty new to these kind of processes).
When I try to access my server in the browser (my DNS:9080) the browser says Cannot GET / and the CLI says info: [http] 96.2xx.xxx.xxx - GET / HTTP/1.1 404 139 - 0.521 ms
The security groups for my ec2 instance are:
HTTP / TCP / 80 / 0.0.0.0/0
SSH / TCP / 22 / 0.0.0.0/0
Custom UDP Rule / UDP / 9080 / 0.0.0.0/0
Custom TCP Rule / TCP / 9080 / 0.0.0.0/0
I'm stuck. What am I doing wrong? Thanks for your help.
The web based dashboard was part of ROS 1.x, but was replaced by Realm Studio in ROS 2.0.

Resources