Talk:Parsoid/2018
Add topic| This page used the Structured Discussions extension to give structured discussions. It has since been converted to wikitext, so the content and history here are only an approximation of what was actually displayed at the time these comments were made. |
Report a new bug in Phabricator
Previous discussion was archived at Talk:Parsoid/Archive on 24 June 2015.
Parsoid getting requests from client IP, not localhost or server's IP
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hi, I followed the diagnostic step from Talk:Parsoid/2017#h-Parsoid_and_Private_wiki-2017-05-24T13:44:00.000Z.
Except when Parsoid gives me the "Invalid domain" error, it shows me a different one in the log, depending on whoever the client is.
How can I circumvent that? Goymaster (talk) 15:04, 29 January 2018 (UTC)
- The invalid domain error usually means that there isn't a MediaWiki API setup in Parsoid's config for the specified path. Can you provide some examples of the url you're requesting and the errors? Arlolra (talk) 16:55, 29 January 2018 (UTC)
- I just added a VirtualHost *:8000 to handle all wildcards that match \api.php(.*)
- It seems to be working fine so far. Goymaster (talk) 23:44, 29 January 2018 (UTC)
mediawiki into virtual machine problem with visualeditor
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
I have installed mediawiki in a VM (ubuntu server 16.04) following setup given in mediawiki website. Files config.yaml and LocalSettings.php have the same 'domain' tag and the urls are reaching the correct site. As I connect from the host system I make some port forward on the VM network
host (browser) port guest (VM) port
127.0.0.1 2222 10.0.2.34 22
127.0.0.1 8081 10.0.2.34 80
127.0.0.1 8142 10.0.2.34 8142
I browe through the site ok, but when I try to edit a page with visualeditor, I get this error
Error loading data from server: apierror-visualeditor-docserver-http: HTTP 500
And in parsoid.log I get this:
{"name":"../src/lib/index.js","hostname":"pc","pid":3697,"level":40,"logType":"warn/api","wiki":"wiki$0","title":"Main_Page","oldId":null,"reqId":null,"userAgent":"VisualEditor-MediaWiki/1.30.0","msg":"Failed API request, {\"error\":{},\"retries-remaining\":1}","longMsg":"Failed API request,\n{\"error\":{},\"retries-remaining\":1}","levelPath":"warn/api","time":"2018-02-06T00:14:34.873Z","v":0}
{"name":"../src/lib/index.js","hostname":"pc","pid":3697,"level":40,"logType":"warn/api","wiki":"wiki$0","title":"Main_Page","oldId":null,"reqId":null,"userAgent":"VisualEditor-MediaWiki/1.30.0","msg":"Failed API request, {\"error\":{},\"retries-remaining\":0}","longMsg":"Failed API request,\n{\"error\":{},\"retries-remaining\":0}","levelPath":"warn/api","time":"2018-02-06T00:14:34.876Z","v":0}
{"name":"parsoid","hostname":"pc","pid":3697,"level":60,"err":{"message":"Config Request failure for \"uri\": Error: Invalid URI \"uri\"","name":"../src/lib/index.js","stack":"../src/lib/index.js: Config Request failure for \"uri\": Error: Invalid URI \"uri\"\n at ConfigRequest.ApiRequest._requestCB (/usr/lib/parsoid/src/lib/mw/ApiRequest.js:415:15)\n at self.callback (/usr/lib/parsoid/node_modules/request/request.js:186:22)\n at emitOne (events.js:96:13)\n at Request.emit (events.js:188:7)\n at Request.init (/usr/lib/parsoid/node_modules/request/request.js:274:17)\n at new Request (/usr/lib/parsoid/node_modules/request/request.js:128:8)\n at request (/usr/lib/parsoid/node_modules/request/index.js:53:10)\n at ConfigRequest.ApiRequest.request (/usr/lib/parsoid/src/lib/mw/ApiRequest.js:336:9)\n at ConfigRequest.ApiRequest._requestCB (/usr/lib/parsoid/src/lib/mw/ApiRequest.js:412:9)\n at self.callback (/usr/lib/parsoid/node_modules/request/request.js:186:22)\n at emitOne (events.js:96:13)\n at Request.emit (events.js:188:7)\n at Request.init (/usr/lib/parsoid/node_modules/request/request.js:274:17)\n at new Request (/usr/lib/parsoid/node_modules/request/request.js:128:8)\n at request (/usr/lib/parsoid/node_modules/request/index.js:53:10)\n at ConfigRequest.ApiRequest.request (/usr/lib/parsoid/src/lib/mw/ApiRequest.js:336:9)","levelPath":"fatal/request"},"msg":"Config Request failure for \"uri\": Error: Invalid URI \"uri\"","time":"2018-02-06T00:14:34.881Z","v":0}
Any help please!?
Thanks 37.134.155.9 (talk) 01:14, 6 February 2018 (UTC)
Error: Invalid URI \"uri\""suggests something might be wrong with you config.yaml- Can you post what you have for mwApis? Arlolra (talk) 01:40, 6 February 2018 (UTC)
- In fact, if I change uri value to be something different , even with no sense, the error is the same.
- In mwApis (config.yaml) I have this:
- mwApis:
- - # This is the only required parameter,
- # the URL of you MediaWiki API endpoint.
- uri: 'http://127.0.0.1:8081/mediawiki/api.php'
- # The "domain" ...
- domain: 'localhost' # optional
- And in wgVirtualRestConfig (LocalSettings,php):
- $wgVirtualRestConfig['modules']['parsoid'] = array(
- 'url' => 'http://127.0.0.1:8142',
- 'domain' => 'localhost',
- 'prefix' => 'localhost'
- ); 46.222.181.232 (talk) 08:41, 6 February 2018 (UTC)
- Do you maybe have localsettings.js lying around as well? Parsoid might be picking that up. Or, maybe the config.yaml you're editing isn't the right one (since changing it should have some effect)? Arlolra (talk) 15:05, 6 February 2018 (UTC)
- I'm sorry the message is the same in the web page, but not in parsoid.log. I find another config file but seeing its contents, I think I has nothing to do.
- sudo find / -name config.yaml
- /usr/lib/parsoid/node_modules/service-runner/config.yaml
- /etc/mediawiki/parsoid/config.yaml
- But
- sudo find / -name localsettings.js
- gives me nothing.
- I've made another test:
- sudo systemctl stop parsoid.service
- sudo rm /var/log/parsoid/parsoid.log
- sudo nano /etc/mediawiki/parsoid/config.yaml
- (I set the urls as in my first post)
- sudo systemctl start parsoid.service
- I load main page in wiki site, and try to edit it, the same error appears y de web page. Now I get this error (which I had also seen before).
- {"name":"../src/lib/index.js","hostname":"pc","pid":1753,"level":40,"logType":"warn/api/econnrefused","wiki":"wiki$0","title":"Main_Page","oldId":null,"reqId":null,"userAgent":"VisualEditor-MediaWiki/1.30.0","msg":"Failed API request, {\"error\":{\"code\":\"ECONNREFUSED\",\"errno\":\"ECONNREFUSED\",\"syscall\":\"connect\",\"address\":\"127.0.0.1\",\"port\":8081},\"retries-remaining\":1}","longMsg":"Failed API request,\n{\"error\":{\"code\":\"ECONNREFUSED\",\"errno\":\"ECONNREFUSED\",\"syscall\":\"connect\",\"address\":\"127.0.0.1\",\"port\":8081},\"retries-remaining\":1}","levelPath":"warn/api/econnrefused","time":"2018-02-06T17:54:20.001Z","v":0}
- {"name":"../src/lib/index.js","hostname":"pc","pid":1753,"level":40,"logType":"warn/api/econnrefused","wiki":"wiki$0","title":"Main_Page","oldId":null,"reqId":null,"userAgent":"VisualEditor-MediaWiki/1.30.0","msg":"Failed API request, {\"error\":{\"code\":\"ECONNREFUSED\",\"errno\":\"ECONNREFUSED\",\"syscall\":\"connect\",\"address\":\"127.0.0.1\",\"port\":8081},\"retries-remaining\":0}","longMsg":"Failed API request,\n{\"error\":{\"code\":\"ECONNREFUSED\",\"errno\":\"ECONNREFUSED\",\"syscall\":\"connect\",\"address\":\"127.0.0.1\",\"port\":8081},\"retries-remaining\":0}","levelPath":"warn/api/econnrefused","time":"2018-02-06T17:54:20.016Z","v":0}
- {"name":"parsoid","hostname":"pc","pid":1753,"level":60,"err":{"message":"Config Request failure for \"http://127.0.0.1:8081/mediawiki/api.php\": Error: connect ECONNREFUSED 127.0.0.1:8081","name":"../src/lib/index.js","stack":"../src/lib/index.js: Config Request failure for \"http://127.0.0.1:8081/mediawiki/api.php\": Error: connect ECONNREFUSED 127.0.0.1:8081\n at ConfigRequest.ApiRequest._requestCB (/usr/lib/parsoid/src/lib/mw/ApiRequest.js:415:15)\n at self.callback (/usr/lib/parsoid/node_modules/request/request.js:186:22)\n at emitOne (events.js:96:13)\n at Request.emit (events.js:188:7)\n at Request.onRequestError (/usr/lib/parsoid/node_modules/request/request.js:878:8)\n at emitOne (events.js:101:20)\n at ClientRequest.emit (events.js:188:7)\n at Socket.socketErrorListener (_http_client.js:310:9)\n at emitOne (events.js:96:13)\n at Socket.emit (events.js:188:7)\n at emitErrorNT (net.js:1281:8)\n at _combinedTickCallback (internal/process/next_tick.js:80:11)\n at process._tickCallback (internal/process/next_tick.js:104:9)","levelPath":"fatal/request"},"msg":"Config Request failure for \"http://127.0.0.1:8081/mediawiki/api.php\": Error: connect ECONNREFUSED 127.0.0.1:8081","time":"2018-02-06T17:54:20.021Z","v":0} 37.134.155.9 (talk) 18:05, 6 February 2018 (UTC)
- Parsoid is having trouble connecting to your MediaWiki API at http://127.0.0.1:8081/mediawiki/api.php
- Are you sure that url works? What happens when you curl it from the same machine Parsoid is running on? Arlolra (talk) 22:10, 6 February 2018 (UTC)
- That was the point, I was only testing that url on the host machine.
- I 've changed Apache to listen on 8081 and the port forward of that VM (guest) to be listening on that port and now it works!
- Thanks a lot for your support!! 37.134.155.9 (talk) 23:29, 6 February 2018 (UTC)
- "37.134.155.9", I'm done. I've had it. I'm not messing with trying to install visual editor any more. If you have a vm with visual editor working, I would be ultimately graced by your kindness if I could have a copy of it. I am willing to reimburse your for your time in making it as it is wasting my time/money. Please let me know. Thank you. Djmaxx007 (talk) 04:11, 10 April 2018 (UTC)
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
It will be nice to get this released to the public with a new version of parsoid if that is what I think it is. :) [[kgh]] (talk) 21:24, 11 February 2018 (UTC)
- Parsoid already supported sites with self-signed certs. This was just to make it configurable per wiki, rather than for all mwApis. Arlolra (talk) 21:27, 22 February 2018 (UTC)
- Thanks for your insight! This however is still an improvement I believe. [[kgh]] (talk) 09:12, 23 February 2018 (UTC)
- We'll put out a release in March that includes this improvement.
- https://lists.wikimedia.org/pipermail/wikitech-l/2018-February/089543.html Arlolra (talk) 17:39, 26 February 2018 (UTC)
help with Command line testing of the Parsoid node
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Please help, I am trying to troubleshoot my Parsoid node from the command line.
From the CLI of my Centos7 host:
1) when I type netstat -plntu
I am able to confirm that Parsoid is running on port 8000
tcp6 0 0 :::8000 :::* LISTEN 27853/node
2) when I type: curl http://127.0.0.1/mywiki/api.php
the response is the expected html page code of the api.php page
3) when I type curl http://127.0.0.1:8000/version
it responds with the appropriate Parsoid version info:
{"name":"parsoid","version":"0.7.1+git","sha":"a47a89845a93b4cd1fa961494d156f2555ce2531"}
4) but when I run: curl -L http://127.0.0.1:8000/localhost/v3/page/html/Main_Page/
it fails with:
error: Failed to parse the JSON response for Config Request path: /localhost/v3/page/html/Main_Page/ lib/index.js: Failed to parse the JSON response for Config Request at ConfigRequest.ApiRequest._handleBody (/opt/parsoid/lib/mw/ApiRequest.js:470:12) at ConfigRequest.ApiRequest._requestCB (/opt/parsoid/lib/mw/ApiRequest.js:421:8) at Request.self.callback (/opt/parsoid/node_modules/request/request.js:186:22) at emitTwo (events.js:106:13) at Request.emit (events.js:191:7) at Request.<anonymous> (/opt/parsoid/node_modules/request/request.js:1163:10) at emitOne (events.js:96:13) at Request.emit (events.js:188:7) at IncomingMessage.<anonymous> (/opt/parsoid/node_modules/request/request.js:1085:12) at IncomingMessage.g (events.js:292:16) at emitNone (events.js:91:20) at IncomingMessage.emit (events.js:185:7) at endReadableNT (_stream_readable.js:974:12) at _combinedTickCallback (internal/process/next_tick.js:80:11) at process._tickCallback (internal/process/next_tick.js:104:9)
my config.yaml is configured as:
uri: 'http://127.0.0.1/mywiki/api.php' domain: 'localhost'and my localsettings.php is configured as:
if ( $REMOTE_ADDR == '127.0.0.1' ) { $wgGroupPermissions['*']['read'] = true; $wgGroupPermissions['*']['edit'] = true; }
wfLoadExtension( 'VisualEditor' );
$wgDefaultUserOptions['visualeditor-enable'] = 1;
$wgDefaultUserOptions['visualeditor-editor'] = "visualeditor";
$wgHiddenPrefs[] = 'visualeditor-enable';
$wgDefaultUserOptions['visualeditor-enable-experimental'] = 1;
$wgVirtualRestConfig['modules']['parsoid'] = array(
'url' => 'http://localhost:8000',
'domain' => 'localhost',
'prefix' => 'localhost'
);
$wgVisualEditorAvailableNamespaces = [
NS_MAIN => true,
NS_TALK => true,
NS_USER => true,
"_merge_strategy" => "array_plus"
];
$wgSessionsInObjectCache = true;
$wgVirtualRestConfig['modules']['parsoid']['forwardCookies'] = true;
here is npm version:
/opt/parsoid/ #npm version
{ parsoid: '0.8.0+git',
npm: '3.10.10',
ares: '1.10.1-DEV',
http_parser: '2.7.1',
icu: '50.1.2',
modules: '48',
node: '6.12.3',
openssl: '1.0.2k-fips',
uv: '1.10.2',
v8: '5.1.281.111',
zlib: '1.2.7' }
Questions:
- What could cause the "Failed to parse the JSON response for Config Request path" error?
- What other information could be relevant to the command line testing of the Parsoid
- What other tests can I run?
- Where are the Parsoid errors being logged? Revansx (talk) 17:21, 22 February 2018 (UTC)
- trying to work through the information at: Extension talk:VisualEditor/2017/12#h-VisualEditor_doesn't_work_with_wiki_markups_since_MW_1.29.2-2017-12-01T19:12:00.000Z to no avail. Revansx (talk) 18:20, 22 February 2018 (UTC)
- 1) The request is being responded to with something other than JSON.
- The config request is similar to,
- http://127.0.0.1/pbswiki/api.php?action=query&meta=siteinfo&format=json
- Does that work? Does it return parseable JSON? Are there any warnings or additional characters leaking in from your LocalSettings.php?
- 2) Above, the path you tested in 2. was mywiki but your config.yaml says pbswiki
- 3) Try disabling all your extensions so that it's just Parsoid talking to the MediaWiki api and if that works, slowly re-enabled them.
- 4) Depends how you installed / are running the service. The default is just stderr though. Arlolra (talk) 18:26, 22 February 2018 (UTC)
- 1a. yes. "http://127.0.0.1/mywiki/api.php?action=query&meta=siteinfo&format=json" works, but
- 1b. No. the response is not JSON, it appears to be the html of the API page..
- ... any idea why that happens?
- 2. *derp* .. ignore that please.. pbswiki is indeed the actual install name.. I'm tying to avoid sharing the actual site name when I share error messages and configuration settings.. i'm not always as thorough as I wish I was..
- 3. will do.
- 4. hmm.. i haven't done anything specific for a log file.. it is whatever the defaults are.. there isn't anything in config.yaml that sets a log file name and path. should there be? Revansx (talk) 19:51, 22 February 2018 (UTC)
- so... somewhat unrelated, I attempted to get the raw wiki text of an artcile from cURL using:
curl http://127.0.0.1/mywiki/index.php?title=Test&action=raw
- and it resulted with just the "index.php" html which I thought was strange because (regardless of parsoid) curl should be able to do that easily (right?)... and so I looked-up how to send POST data with a CURL commands and tried this:
curl --data "title=Test&action=raw" http://127.0.0.1/mywiki/index.php
- to which the response was:
<html> <head><title>405 Not Allowed</title></head> <body bgcolor="white"> <center><h1>405 Not Allowed</h1></center> <hr><center>nginx/1.12.2</center> </body> </html>
- ...could this "405 Not Allowed" be happening to the JSON request? or is this nothing. Revansx (talk) 20:49, 22 February 2018 (UTC)
- In order to assist in debugging, I ran
[/opt/parsoid] #npm install log
per: "https://www.npmjs.com/package/log". Now I need to learn how to get it make log entries and how/where to read them. Revansx (talk) 21:03, 22 February 2018 (UTC) - From 1b above, it seems like your MediaWiki instance isn't installed correctly. Maybe whatever your webserver sitting in front of it is (Apache?) isn't passing the querystring parameters?
- Whatever the case, you need to resolve that first before trying to get Parsoid to work. That config request should return JSON. Arlolra (talk) 21:15, 22 February 2018 (UTC)
- ok.. that gives me something new to figure out.. Do you by chance know how to perform a "wikitext to html" conversion with "nodejs" at the command line? Revansx (talk) 23:37, 22 February 2018 (UTC)
- With Parsoid, yes, it's
echo "my '''wikitext'''" | node bin/parse --wt2html --offlineArlolra (talk) 00:19, 23 February 2018 (UTC) - That worked!!! :-)
[/opt/parsoid] #echo "my '''wikitext'''" | node bin/parse --wt2html --offline
- produced
<!DOCTYPE html> <html prefix="dc: http://purl.org/dc/terms/ mw: http://mediawiki.org/rdf/"><head prefix="mwr: http://en.wikipedia.org/wiki/Special:Redirect/"><meta charset="utf-8"/><meta property="mw:pageNamespace" content="0"/><meta property="isMainPage" content="true"/><meta property="mw:html:version" content="1.6.0"/><link rel="dc:isVersionOf" href="//en.wikipedia.org/wiki/Main%20Page"/><title></title><base href="//en.wikipedia.org/wiki/"/><link rel="stylesheet" href="//en.wikipedia.org/w/load.php?modules=mediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.skinning.content.parsoid%7Cmediawiki.skinning.interface%7Cskins.vector.styles%7Csite.styles%7Cext.cite.style%7Cext.cite.styles%7Cmediawiki.page.gallery.styles&only=styles&skin=vector"/><!--[if lt IE 9]><script src="//en.wikipedia.org/w/load.php?modules=html5shiv&only=scripts&skin=vector&sync=1"></script><script>html5.addElements('figure-inline');</script><![endif]--></head><body data-parsoid='{"dsr":[0,18,0,0]}' lang="en" class="mw-content-ltr sitedir-ltr ltr mw-body-content parsoid-body mediawiki mw-parser-output" dir="ltr"><p data-parsoid='{"dsr":[0,17,0,0]}'>my <b data-parsoid='{"dsr":[3,17,3,3]}'>wikitext</b></p> </body></html>- .. Thank you!!
and so then I tried: [/opt/parsoid] #echo "<html><head><title>Test</title></head><body><table><tr><td>A</td><td>B</td></tr></table></body></html>" | node bin/parse --html2wt --offline
- which produced
{| |A |B |}- Yay! Revansx (talk) 17:35, 23 February 2018 (UTC)
- ok.. now I'm convinced the original problem is an issue with my servers configuration.. stay tuned! Revansx (talk) 17:39, 23 February 2018 (UTC)
- But note, the --offline prevents fetching any info from the MediaWiki API so you'll want to get the above fixed to use it in the context of your wiki. Arlolra (talk) 17:40, 23 February 2018 (UTC)
- gotcha! .. it's still a great test.. I'm hoping that I can capture here all of the command line tests that one can run to systematically troubleshoot a nodejs, parsoid, VE issue and quickly show where the problem lies. If I understand right, you are saying I can remove the "--offline" switch and replace it with wiki specific info and do the same thing, right? Revansx (talk) 17:57, 23 February 2018 (UTC)
- I'm saying templates and images, etc. won't resolve in offline mode. The parser is more useful when it has a mediawiki api to fetch info from. Arlolra (talk) 21:47, 23 February 2018 (UTC)
- ok, so.. i used your example to create this api url for wikipedia:
https://en.wikipedia.org/w/api.php?action=query&meta=siteinfo&format=json
- and it produced this result:
{"batchcomplete":"","query":{"general":{"mainpage":"Main Page","base":"https://en.wikipedia.org/wiki/Main_Page","sitename":"Wikipedia","logo":"//en.wikipedia.org/static/images/project-logos/enwiki.png","generator":"MediaWiki 1.31.0-wmf.22","phpversion":"5.6.99-hhvm","phpsapi":"srv","hhvmversion":"3.18.6-dev","dbtype":"mysql","dbversion":"10.0.34-MariaDB","imagewhitelistenabled":"","langconversion":"","titleconversion":"","linkprefixcharset":"","linkprefix":"","linktrail":"/^([a-z]+)(.*)$/sD","legaltitlechars":" %!\"$&'()*,\\-.\\/0-9:;=?@A-Z\\\\^_`a-z~\\x80-\\xFF+","invalidusernamechars":"@:","fixarabicunicode":"","fixmalayalamunicode":"","git-hash":"fd29ac30b061c6e0c6590eed98f700a4e829a424","git-branch":"wmf/1.31.0-wmf.22","case":"first-letter","lang":"en","fallback":[],"fallback8bitEncoding":"windows-1252","writeapi":"","maxarticlesize":2097152,"timezone":"UTC","timeoffset":0,"articlepath":"/wiki/$1","scriptpath":"/w","script":"/w/index.php","variantarticlepath":false,"server":"//en.wikipedia.org","servername":"en.wikipedia.org","wikiid":"enwiki","time":"2018-02-26T02:08:54Z","misermode":"","uploadsenabled":"","maxuploadsize":4294967296,"minuploadchunksize":1024,"galleryoptions":{"imagesPerRow":0,"imageWidth":120,"imageHeight":120,"captionLength":"","showBytes":"","mode":"traditional","showDimensions":""},"thumblimits":[120,150,180,200,220,250,300,400],"imagelimits":[{"width":320,"height":240},{"width":640,"height":480},{"width":800,"height":600},{"width":1024,"height":768},{"width":1280,"height":1024}],"favicon":"//en.wikipedia.org/static/favicon/wikipedia.ico","centralidlookupprovider":"CentralAuth","allcentralidlookupproviders":["CentralAuth","local"],"interwikimagic":"","magiclinks":{"ISBN":"","PMID":"","RFC":""},"categorycollation":"uca-default-u-kn","wmf-config":{"wmfMasterDatacenter":"eqiad"},"citeresponsivereferences":"","linter":{"high":["deletable-table-tag","html5-misnesting","misc-tidy-replacement-issues","multiline-html-table-in-list","multiple-unclosed-formatting-tags","pwrap-bug-workaround","self-closed-tag","tidy-font-bug","tidy-whitespace-bug","unclosed-quotes-in-heading"],"medium":["bogus-image-options","fostered","misnested-tag","multi-colon-escape"],"low":["missing-end-tag","obsolete-tag","stripped-tag"]},"mobileserver":"https://en.m.wikipedia.org","pageviewservice-supported-metrics":{"pageviews":{"pageviews":""},"siteviews":{"pageviews":"","uniques":""},"mostviewed":{"pageviews":""}},"readinglists-config":{"maxListsPerUser":100,"maxEntriesPerList":1000,"deletedRetentionDays":30}}}}- would you expect this to be similar to the result of the cURL command on my 127.0.0.1 command? Revansx (talk) 02:14, 26 February 2018 (UTC)
- It just dawned on me that I need to enable php on nginx :-) .. as strange as this sounds.. I run 2 web servers:
- I run nginx for loop-back/localhost api calls
- and I run apache for all external client user access.
- I do this because my server has a Security policy that says that all incoming calls to the server must have a session that is validated by a remote authentication server. This means that any server-side activity (like parsoid) using apache port 80 or 443 gets caught-up in the redirect in an attempt to force the user to achieve a validated session. I have no control over this. So, I am attempting to solve the problem by running 2 web-servers. External visitors with validated sessions use SSL apache on port 443 and localhost calls use nginx on port 8080. If that sounds crazy, then all I can say, is, I'm all ears if you know a better way to get parsoid running on a private enterprise wiki with a security policy that enforces remotely secured sessions. please let me know! :-) Revansx (talk) 02:33, 26 February 2018 (UTC)
- How are sessions enforced? There's this section on forwarding cookies,
- Extension:VisualEditor#Forwarding Cookies to Parsoid
- But I'm going to assume that after including fastcgi params in your nginx config, this is all working. Arlolra (talk) 15:53, 26 February 2018 (UTC)
- Yes. I solved the problem. My enterprise server environment is tricky to say the least. I have a Policy Agent running that intercepts all traffic and forwards it to a remote identity provider which enforces the session header and then routes the user back to the site for auto-login consuming the session attributes via the Remote_Auth extension.. this has been a very tricky obstacle for me in developing good command line troubleshooting techniques. I slugged through getting the parsoid service working as a sole site, but now I'm trying to install multiple sites and alter my config.yaml to host multiple wikis.. that's when everything broke on me and I wanted to troubleshoot the parsoid service from the CLI irrespective of the wiki site(s). That's why I set-up the nginx server.. so that I could have a web-server that I could talk to from the CLI that didn't have the hassles of the Policy Agent to contend with. Revansx (talk) 17:11, 26 February 2018 (UTC)
- the command
[/opt/parsoid]# curl -L http://127.0.0.1:8000/localhost/v3/page/html/Test
- now produces the expected response:
<!DOCTYPE html> <html prefix="dc: http://purl.org/dc/terms/ mw: http://mediawiki.org/rdf/" about="https://mywiki.mycompany.com/smw/Special:Redirect/revision/20526"><head prefix="mwr: https://mywiki.mycompany.com/smw/Special:Redirect/"><meta charset="utf-8"/><meta property="mw:pageNamespace" content="0"/><meta property="mw:pageId" content="7458"/><link rel="dc:replaces" resource="mwr:revision/20496"/><meta property="dc:modified" content="2018-02-22T19:40:20.000Z"/><meta property="mw:revisionSHA1" content="1e0bc0a9623dd93bb05ca2e0d4b3862b6859e406"/><meta property="mw:html:version" content="1.6.0"/><link rel="dc:isVersionOf" href="https://mywiki.mycompany.com/smw/Test"/><title>Test</title><base href="https://mywiki.mycompany.com/smw/"/><link rel="stylesheet" href="//mywiki.mycompany.com/mywiki/load.php?modules=mediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.skinning.content.parsoid%7Cmediawiki.skinning.interface%7Cskins.vector.styles%7Csite.styles%7Cext.cite.style%7Cext.cite.styles%7Cmediawiki.page.gallery.styles&amp;only=styles&amp;skin=vector"/><!--[if lt IE 9]><script src="//mywiki.mycompany.com/mywiki/load.php?modules=html5shiv&only=scripts&skin=vector&sync=1"></script><script>html5.addElements('figure-inline');</script><![endif]--><nowiki></head></nowiki><nowiki><body data-parsoid='{"dsr":[0,10,0,0]}' lang="en" class="mw-content-ltr sitedir-ltr ltr mw-body-content parsoid-body mediawiki mw-parser-output" dir="ltr"></nowiki><section data-mw-section-id="0" data-parsoid="{}"><p data-parsoid='{"dsr":[0,10,0,0]}'>test 1 2 3</p></section></body></html>- my nodejs now works at the command line (per the above command)
- both my VisualEditors now work in both wikis hosted on the same server with a single parsoid node.
- ... thanks! Revansx (talk) 17:27, 26 February 2018 (UTC)
Why not just install through npm?
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Is there a reason why the documented way of setting up Parsoid is through a custom package manager rather than just doing an `npm install`? Njk (talk) 16:26, 25 February 2018 (UTC)
- Not every hosting provider allows you to npm install. The debian package comes with an init script and sets up logging and bundled dependencies. Arlolra (talk) 16:43, 25 February 2018 (UTC)
Issue With starting on boot with CentOS 6
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
hi, i have parsoid all working and installed with CentOS, everything works fine, except i can't figure out how to re-launch the service on boot, i have tried mp2 however it seems to keep stoping and restarting the service and despite it says its running on mp2 process list it doesn't connect.
at the moment I'm launching it in an other screen in shell and letting it run, but this isn't probably the best way to achieve this. Stationeers.Wiki (talk) 23:41, 14 March 2018 (UTC)
- If it's starting and stopping in a loop, it probably means it's crashing. What do you see in the logs? Maybe the port it's trying to bind to is already in use? Arlolra (talk) 00:18, 15 March 2018 (UTC)
- when i run
- "node --max-old-space-size=128 bin/server.js -n 1"
- it works fine, but without --max-old-space-size=128 it crashes Stationeers.Wiki (talk) 00:28, 15 March 2018 (UTC)
- Is that true in your screen also? How much ram is available on your server? Arlolra (talk) 00:30, 15 March 2018 (UTC)
- 2GB , but for the last 5 hours with the command "node --max-old-space-size=128 bin/server.js -n 1" it works perfect Stationeers.Wiki (talk) 00:32, 15 March 2018 (UTC)
- 2GB free? That command starts two processes (master/worker), each with a 2GB memory limit (I believe) but they shouldn't be using that at startup. Arlolra (talk) 15:53, 15 March 2018 (UTC)
- this is the output without using --max-old-space-size=128
- {"name":"parsoid","hostname":"s104-238-92-14.secureserver.net","pid":13231,"level":60,"err":{"message":"Cannot read property 'pid' of undefined","name":"TypeError","stack":"TypeError: Cannot read property 'pid' of undefined\n at Worker.startupWorkerExit (/root/parsoid/node_modules/service-runner/lib/master.js:184:57)\n at Worker.emit (events.js:180:13)\n at ChildProcess.worker.process.once (internal/cluster/master.js:190:12)\n at Object.onceWrapper (events.js:272:13)\n at ChildProcess.emit (events.js:180:13)\n at Process.ChildProcess._handle.onexit (internal/child_process.js:209:12)","levelPath":"fatal/service-runner/unhandled"},"msg":"Cannot read property 'pid' of undefined","time":"2018-03-15T00:31:05.078Z","v":0} Stationeers.Wiki (talk) 00:31, 15 March 2018 (UTC)
- Hmm, well the error reporting there is broken. I filed https://github.com/wikimedia/service-runner/pull/182 Arlolra (talk) 15:51, 15 March 2018 (UTC)
- thanks!
- will this require a software update? Stationeers.Wiki (talk) 16:25, 15 March 2018 (UTC)
- Yes, but that won't fix your problem, only help in diagnosing. But if you're getting success by limiting how big the heap can grow, I'm guessing there just isn't even enough free memory to start the worker. Arlolra (talk) 16:31, 15 March 2018 (UTC)
- ah right, ok, thank you! will close this topic now! Stationeers.Wiki (talk) 16:39, 15 March 2018 (UTC)
Parsoid on Raspbian : VisualEditor HTTP 500 Error
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hello,
I'm setting up a mediawiki on my Raspberry Pi 3, it's run the Raspbian that are based on Debian stretch.
I finished up parsoid installation, but VisualEditor doesn't work.
Mediawiki version : 1.30
php version : 7.0.27-0+deb9u1 (cli) (built: Jan 5 2018 13:51:52)
curl version : 7.52.1 (arm-unknown-linux-gnueabihf)
nvm version : 0.33.8
node version : v8.10.0
npm version : 5.6.0
I don't know why VisualEdit doesn't work.
When I cilck Edit, there's no response from parsoid. Parsoid is up and running but I can't confirm it's linked with VisualEditor.
What am I doing wrong? Any suggestion?
Thanks. Alkydes (talk) 22:24, 17 March 2018 (UTC)
- curl was the answer.
- $ sudo apt-get install php-curl Alkydes (talk) 06:54, 18 March 2018 (UTC)
VisualEditor stopped working after upgrade to parsoid 0.9.0all
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
mediawiki 1.29 on Mint 18.2. VisualEditor 0.1.0 (b655946)
everything was going fine until the upgrade to parsoid 0.9.0all, now I get the error "apierror-visualeditor-docserver-http: HTTP 406" when trying to launch Visual Editing of a page
Something changed in the request syntax needed by parsoid?
Do I miss any dependency? Do I miss any matching between versions Parsoid/VIsualEditor? Luigi.d (talk) 10:16, 24 March 2018 (UTC)
- Sorry, after posting the message above, I've continued to search, and I've found the release 0.9.0 caveats.
- I'll try to upgrade both the wiki and VisualEditor Luigi.d (talk) 10:56, 24 March 2018 (UTC)
Visual Editor newer than December 12, 2017 for parsoid 0.9.0
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
I am looking for a VisualEditor version that works with parsoids 0.9.0 but does not require version 1.31 of MediaWiki. Is there a version after December 12th 2017 but before the 1.31 requirement that can be downloaded or is "apt-mark hold parsoid" the current work around until 1.31 is released to stable? LawrenceSystems (talk) 13:33, 24 March 2018 (UTC)
- apt-mark hold parsoid is your best solution for now if you aren't on MW 1.31 SSastry (WMF) (talk) 13:38, 24 March 2018 (UTC)
Rant: Managing parsoid debian package versions with apt
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
So... there's no way to downgrade to parsoid 0.8.0 using apt.
> sudo apt-get install parsoid=0.8.0all
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Version '0.8.0all' for 'parsoid' was not found
> sudo apt-cache policy parsoid
parsoid:
Installed: 0.9.0all
Candidate: 0.9.0all
Version table:
*** 0.9.0all 500
500 https://releases.wikimedia.org/debian jessie-mediawiki/main amd64 Packages
100 /var/lib/dpkg/status
Why there's not a proper way to handle versions in wikimedia's debian repository?
The only way to downgrade is to download the deb from https://people.wikimedia.org/~ssastry/parsoid/debs/ (and pray that nobody hacked it)
Note that apt-mark hold parsoid doesn't work when you're installing the package for the first time! Ciencia Al Poder (talk) 11:38, 14 April 2018 (UTC)
- We use reprepro to create the Debian repository (not the full dak used by Debian) - I'm not sure whether it supports having multiple versions of a package.
- Providing PGP signatures for https://people.wikimedia.org/~ssastry/parsoid/debs/ (or some better management of older versions) is definitely something we should improve. Legoktm (talk) 20:57, 14 April 2018 (UTC)
installing on machine that is not internet facing
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hi,
I am trying to install Parsoid on a machine that is not facing the internet, it is on a firewalled internal network with no access to the outside world.
So, the question is, is there anyway to install parsoid onto a server that is not internet facing? If so, how?
Any help is appreciated.
Gary Squeak24 (talk) 11:46, 4 May 2018 (UTC)
- OK, I have found this, will have a go. https://www.npmjs.com/package/offline-npm Squeak24 (talk) 13:22, 4 May 2018 (UTC)
- All Parsoid needs is a config to point it to a wiki. It can be an internal / local wiki. In that case, it won't need to access the internet. You can set up the wiki config via config.yaml. See Parsoid/Setup#Configuration SSastry (WMF) (talk) 13:31, 4 May 2018 (UTC)
- The deploy repo has a checkout of all the dependencies,
- https://github.com/wikimedia/mediawiki-services-parsoid-deploy Arlolra (talk) 15:01, 4 May 2018 (UTC)
- Hi Squeak24,
- Can you give me some information about how you performed your install in an offline environment? I'm not that familar with npm Mbrooksham (talk) 11:51, 7 February 2019 (UTC)
Parsoid 0.9.0 update brings 406 only by editing
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hello,
when I try to edit a post I get the above error.
Posting a new topic is no problem.
Here is an excerpt from the log:
{"name":"parsoid","hostname":"v22018034352662523","pid":2319,"level":60,"logType":"fatal/request","wiki":"wiki$0","title":"Hauptseite","oldId":null,"reqId":null,"userAgent":"VisualEditor-MediaWiki/1.30.0","msg":"Not acceptable.\ntext/html; charset=utf-8; profile=\"https://www.mediawiki.org/wiki/Specs/HTML/1.6.1\"\ntext/html; charset=utf-8; profile=\"https://www.mediawiki.org/wiki/Specs/HTML/2.0.0\"\n","stack":"","httpStatus":406,"longMsg":"Not acceptable.\ntext/html; charset=utf-8; profile=\"https://www.mediawiki.org/wiki/Specs/HTML/1.6.1\"\ntext/html; charset=utf-8; profile=\"https://www.mediawiki.org/wiki/Specs/HTML/2.0.0\"\n","levelPath":"fatal/request","time":"2018-05-21T11:34:47.637Z","v":0}
Here's what I've tried:
Anybody have any idea how I can fix this? Tealk (talk) 11:42, 21 May 2018 (UTC)
Upgrading to parsoid 0.8.1
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
What is the recommendation on upgrading to parsoid 0.8.1. I have a parsoid 0.8.0 running installed via Debian packages and will not be able to update to 0.9.0 until the end of this year. That's why parsoid is on hold.
Should I just download parsoid 0.8.1 and install it over 0.8.0 or do you recommend to uninstall parsoid 0.8.0 via packages and install 0.8.1 thereafter? Probably the latter but I would like to be sure. [[kgh]] (talk) 09:05, 7 June 2018 (UTC)
- I think dpkg --install should do the right thing in this case. I verified locally that installing over an 0.8.0 eliminates the reported vulnerabilities. However, if you uninstall and reinstall, make sure to save your config file and restore it afterwards.
- t SSastry (WMF) (talk) 20:25, 7 June 2018 (UTC)
Failed API request with warn/api/esockettimedout with VisualEditor on Windows
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
This is my solution for others having this issue.
Windows machine - Windows Server 2008 R2, PHP 7.1.14 (php-cgi.exe), NodeJS 8.9.1 LTS, Parsoid 0.8.0, MediaWiki 1.30, SQLite database, Firewall open local port 8000 on nodejs.exe This solution is for all having a working VisualEditor but randomly and often gets "Error loading data from server: Could not connect to the server" when opening VisualEditor.
The cause is in enabled caching in LocalSettings.php. Parsoid is calling MediaWiki API but the request may take for bigger and heavily edited pages even 60s+. So, the request fails with "esockettimedout" exception which is subsequently passed to the VisualEditor giving this error popup.
My original failing setting used to be:
$wgMainCacheType = CACHE_DB; $wgMessageCacheType = CACHE_DB; $wgParserCacheType = CACHE_DB; $wgSessionCacheType = CACHE_DB; $wgLanguageConverterCacheType = CACHE_DB;
My new working setting is:
$wgMainCacheType = CACHE_DB; $wgMessageCacheType = CACHE_NONE; $wgParserCacheType = CACHE_NONE; $wgSessionCacheType = CACHE_DB; $wgLanguageConverterCacheType = CACHE_NONE;
I got this inspiration from topic https://www.mediawiki.org/wiki/Talk%3AParsoid/2015b#h-Failed_API_request-2015-07-20T11%3A58%3A00.000Z where @Arlolra was wondering if it is by caching. Czech.Fox (talk) 06:42, 13 June 2018 (UTC)
- Thank you for this!
- Would you like to add it to VisualEditor/Recipes, where someone was trying to collect some tips and tricks? Whatamidoing (WMF) (talk) 21:44, 15 June 2018 (UTC)
Write Permission Denied
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hi, complete novice here. Way over my head. Installed Parsoid and Visual Editor on Mediawiki (Bitnami on AWS). Website says "internal api error" when trying to use VIsual Editor. Using PuTTY to access localsettings and Parsoid config.yaml, but I get back "no write permission". Try looking up settings.js (or localsettings.js) for Parsoid, but those are not found. 73.32.251.160 (talk) 21:32, 20 June 2018 (UTC)
- Did you confirm your wiki was working without the VE/Parsoid combo? Probably a good place to start. Arlolra (talk) 00:34, 21 June 2018 (UTC)
- Welcome. If you're having other problems with installing MediaWiki, then you might also be able to get help at https://discourse-mediawiki.wmflabs.org/ , from the MediaWiki Stakeholders' Group, or at the Project:Support desk. Good luck! Whatamidoing (WMF) (talk) 21:22, 21 June 2018 (UTC)
How to start parsoid automatically for ubuntu 18.04?
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hello
What should I do to activate and start parsoid automatically when the server and client starts working?
ubuntu 18.04
php7.2-fpm & nginx
Thanks Sokote zaman (talk) 22:52, 1 July 2018 (UTC)
- You could try the init scripts from the deployment repo,
- https://github.com/wikimedia/mediawiki-services-parsoid-deploy/tree/master/debian Arlolra (talk) 02:13, 2 July 2018 (UTC)
- thank you. Please explain exactly what to do? Sokote zaman (talk) 03:23, 2 July 2018 (UTC)
- How did you install Parsoid? Arlolra (talk) 16:54, 2 July 2018 (UTC)
- sudo apt install dirmngr
- sudo apt-key advanced --keyserver keys.gnupg.net --recv-keys 90E9F83F22250DD7
- #Ubuntu
- sudo apt-add-repository "deb https://releases.wikimedia.org/debian jessie-mediawiki main"
- apt-get install software-properties-common
- sudo apt install apt-transport-https
- sudo apt update
- sudo apt update && sudo apt install parsoid
- MediaWiki 1.31.0 (e9afac4)
- PHP 7.2.5-0ubuntu0.18.04.1 (fpm-fcgi)
- MariaDB 10.1.29-MariaDB-6
- ICU 60.2
- Lua 5.1.5
- ubuntu 18.04
- localhost
- parsoid version (0.9.0all)
- VisualEditor 0.1.0 (13a585a)
- tanks Sokote zaman (talk) 18:47, 2 July 2018 (UTC)
- In that case, the it should already be running and can controlled with the
servicecommand. Arlolra (talk) 22:47, 2 July 2018 (UTC) - yes
- tanks Sokote zaman (talk) 06:29, 3 July 2018 (UTC)
Parsoid installation problem Ubuntu 14.04
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hi, when i use install command it gives me that output.
The following extra packages will be installed:
parsoid
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Bekircem (talk) 08:07, 8 August 2018 (UTC)
- To clarify, you ran
apt-get install parsoidand it's listing it as an extra package to install? Arlolra (talk) 16:35, 15 August 2018 (UTC)
Resolving Parsoid URI to local file rather than going through the public domainname
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hi, I was just wondering.
Is it possible to configure the URI setting in config.yaml to point to the API locally, rather than using the public address. Parsoid and MediaWiki are both installed on the same machine.
I've been having issues with VisualEditor getting stuck loading, only to time out.
When checking the cmd I get an error saying API Request Failed. Sometimes I also get the error Unacceptable profile string: text/html
I'm running it all on a Windows Server 2012 R2 62.181.223.54 (talk) 06:24, 15 August 2018 (UTC)
- Yes, it's fine to configure a local host. Arlolra (talk) 16:31, 15 August 2018 (UTC)
- I am unable to correctly parse the string so that it manages to find the API file locally.
- http://localhost resolves to nothing so I can't point to the api file that way and I cannot use the file:// path to point to it either, since I receive and error that it is an unsupported format.
- Do I need to set up a new IIS Site that points to the same location as the wiki so that I may use http://localhost/api.php? 62.181.223.54 (talk) 21:22, 19 August 2018 (UTC)
- Yes Arlolra (talk) 14:59, 20 August 2018 (UTC)
- It worked, but unfortunately it did not resolve the issue. Thank you Arlolra regardless. 62.181.223.54 (talk) 15:58, 22 August 2018 (UTC)
- The cycle of a request generally looks like,
- VE (browser) -> MediaWiki API > Parsoid > MediaWiki API (at this point, Parsoid makes some calls back to the MediaWiki API for various bits of information, like config, image info, etc.)
- There's a potential for deadlocks if your server doesn't support some level of concurrency, but I'm not sure that's happening in this case.
- Can you get Parsoid to render a page, independent of VE? Try something like,
curl http://localhost:8000/localhost/v3/page/html/Main_Page- (or, a variation on that based on your setup.) Arlolra (talk) 16:35, 22 August 2018 (UTC)
- @Arlolra I am having similar issues. I've logged a topic above. When I run the curl command you list I get back the same error that I get when I try to use the VE ui on my web browser client. Curl error (7), connection refused. What exactly does this mean and how can I fix it? AslanFrench (talk) 22:01, 18 October 2018 (UTC)
- Let's use the other thread Arlolra (talk) 00:47, 19 October 2018 (UTC)
HTTP Error 500/API Request
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Like several others I've been having issues with HTTP Error 500/API Request ESOCKETTIMEOUT with Parsoid.
It doesn't happen every time i click Edit on VisualEditor, but once every so often.
I've read through the various threads here but none of the solutions seem to work.
I can access localhost:8000 and confirm that Parsoid is running, and I can parse the pages of the wiki.
I am running Windows Server 2012 R2 with IIS 8 as the HTTP Server.
I am running Parsoid 0.9.0
Regarding PHP I have verified that Curl 7.59.0 is up and running (according to my php.php info file)
The wiki is private to edit but not to read. I have gone through the VisualEditor on private wiki section and both tried forwarding the cookies and the current method of authorizing the Parsoid user from localhost.
Here is my Special:Version information
| Product | Version |
|---|---|
| MediaWiki | 1.31.0 |
| PHP | 7.2.7 (cgi-fcgi) |
| SQLite | 3.20.1 |
| Lua | 5.1.4 |
| Special pages | |
|---|---|
| Extension | Version |
| Renameuser | – |
| Replace Text | 1.4.1 |
| Editors | |
| Extension | Version |
| VisualEditor | 0.1.0 (13a585a)01:14, 31 May 2018 |
| WikiEditor | 0.5.1 |
| Parser hooks | |
| Extension | Version |
| CategoryTree | – |
| Cite | – |
| ImageMap | – |
| InputBox | 0.3.0 |
| ParserFunctions | 1.6.0 |
| Scribunto | – (106fbf4)18:24, 15 May 2018 |
| TemplateData | 0.1.2 (61adb16)21:58, 13 July 2018 |
| Media handlers | |
| Extension | Version |
| PDF Handler | – |
| Spam prevention | |
| Extension | Version |
| ConfirmEdit | 1.5.1 |
| SpamBlacklist | – |
| TitleBlacklist | 1.5.0 |
| API | |
| Extension | Version |
| ParsoidBatchAPI | 1.0.0 (c09fdaa)08:05, 14 April 2018 |
| Other | |
| Extension | Version |
| NetworkAuth | 2.1.2 (58ddb5e)23:12, 9 March 2018 |
Here are my settings:
LocalSettings.php
(I've tried using both CACHE_DB and CACHE_ACCEL)$wgMainCacheType = CACHE_DB;
$wgMessageCacheType = CACHE_NONE;
$wgParserCacheType = CACHE_NONE;
$wgSessionCacheType = CACHE_DB;
$wgLanguageConverterCacheType = CACHE_NONE;
$wgVirtualRestConfig['modules']['parsoid'] = array(
// URL to the Parsoid instance
// Use port 8142 if you use the Debian package
'url' => 'http://localhost:8000',
// Parsoid "domain", see below (optional)
'domain' => 'localhost',
// Parsoid "prefix", see below (optional)
'prefix' => 'localhost'
);
require_once "$IP/extensions/NetworkAuth/NetworkAuth.php";
$wgNetworkAuthUsers[] = [
'iprange' => [ '127.0.0.1' ],
'user' => 'Parsoid'
];
//Extensions
$wgSessionsInObjectCache = true;
wfLoadExtension( 'CategoryTree' );
wfLoadExtension( 'Cite' );
wfLoadExtension( 'ConfirmEdit' );
wfLoadExtension( 'ImageMap' );
wfLoadExtension( 'PdfHandler' );
wfLoadExtension( 'Renameuser' );
wfLoadExtension( 'ReplaceText' );
wfLoadExtension( 'SpamBlacklist' );
wfLoadExtension( 'TitleBlacklist' );
wfLoadExtension( 'WikiEditor' );
wfLoadExtension( 'TemplateData' );
wfLoadExtension( 'ParserFunctions' );
wfLoadExtension( 'Scribunto' );
wfLoadExtension( 'InputBox' );
wfLoadExtension( 'ParsoidBatchAPI' );
$wgGroupPermissions['*']['createaccount'] = false;
$wgGroupPermissions['*']['edit'] = false;
$wgGroupPermissions['*']['read'] = true;config.yamlworker_heartbeat_timeout: 300000In the parsoid cmd window I receive the following errormessage:mwApis:
uri: 'http://localhost/api.php'domain: 'localhost' # optional
{"name":"parsoid","hostname":"$HOSTNAME","pid":808,"level":40,"levelPath":"warn/service-runner","msg":"startup finished","time":"2018-08-22T16:15:43.750Z","v":0}
{"name":"parsoid","hostname":"$HOSTNAME","pid":600,"level":60,"err":{"message":"API response Error for ConfigRequest: request=; error={\"code\":\"internal_api_error_DBQueryError\",\"info\":\"[c6eb657c71f3558d1e84d16b] Database query error.\"}",
"name":"lib/index.js","stack":"lib/index.js: API response Error for ConfigRequest: request=; error={\"code\":\"internal_api_error_DBQueryError\",\"info\":\"[c6eb657c71f3558d1e84d16b]
Database query error.\"}\n at ConfigRequest.ApiRequest._errorObj (C:\\Users\\Administrator\\node_modules\\parsoid\\lib\\mw\\ApiRequest.js:347:9)\n
at ConfigRequest._handleJSON (C:\\Users\\Administrator\\node_modules\\parsoid\\lib\\mw\\ApiRequest.js:919:18)\n
at ConfigRequest.ApiRequest._logWarningsAndHandleJSON (C:\\Users\\Administrator\\node_modules\\parsoid\\lib\\mw\\ApiRequest.js:438:7)\n
at ConfigRequest.ApiRequest._handleBody (C:\\Users\\Administrator\\node_modules\\parsoid\\lib\\mw\\ApiRequest.js:474:7)\n
at ConfigRequest.ApiRequest._requestCB (C:\\Users\\Administrator\\node_modules\\parsoid\\lib\\mw\\ApiRequest.js:417:8)\n
at Request.self.callback (C:\\Users\\Administrator\\node_modules\\parsoid\\node_modules\\request\\request.js:186:22)\n
at emitTwo (events.js:126:13)\n
at Request.emit (events.js:214:7)\n
at Request.<anonymous> (C:\\Users\\Administrator\\node_modules\\parsoid\\node_modules\\request\\request.js:1163:10)\n
at emitOne (events.js:116:13)\n
at Request.emit (events.js:211:7)\n
at IncomingMessage.<anonymous> (C:\\Users\\Administrator\\node_modules\\parsoid\\node_modules\\request\\request.js:1085:12)\n
at Object.onceWrapper (events.js:313:30)\n
at emitNone (events.js:111:20)\n
at IncomingMessage.emit (events.js:208:7)\n
at endReadableNT (_stream_readable.js:1064:12)","levelPath":"fatal/request"},"msg":"API response Error for ConfigRequest: request=; error={\"code\":\"internal_api_error_DBQueryError\",\"info\":\"[c6eb657c71f3558d1e84d16b] Database query error.\"}","time":"2018-08-22T16:15
- 58.500Z","v":0}
$HOSTNAME is the computers hostname. BadDevilGrind (talk) 16:48, 22 August 2018 (UTC)
- The error that the MediaWiki API is returning to Parsoid is
internal_api_error_DBQueryErrorwith the message "Database query error." - I see that you're using SQLite. I'm not sure how well tested MediaWiki is with SQLite.
- See https://lists.wikimedia.org/pipermail/wikitech-l/2018-August/090460.html
- and https://phabricator.wikimedia.org/T191035
- My suggestion would be to use MariaDB since that's what the WMF uses in production. Arlolra (talk) 19:22, 22 August 2018 (UTC)
- I'll try using that.
- Any tips for the migration process from SQLLite to MySQL?
- EDIT: I think I managed to successfully migrate the Wiki.
- I simply copied the wiki folder before dumping the pages into a .xml and removed the LocalSettings to run trough the config script again and set up the Wiki with MariaDB. Afterwards I imported the dump.xml and imported the images.
- Regardless, the VisualEditor and Parsoid seems to be working now. Thank you very much Arlolra. BadDevilGrind (talk) 20:12, 22 August 2018 (UTC)
Tutorial for heroku/glitch.io?
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Finally! After 1 year with pc reset, I got parsoid with no npm erroors (warnings doesn't effect it too much)! Now, because I need to get parsoid live with visual editor without keeping the device on, I found 2 hosting providers (plans for free), well yeah, I will use them for visual editor live, but how? John Harry Lau (talk) 13:41, 9 September 2018 (UTC)
- Unfortunately we cannot provide this level of service. If you're experiencing specific issues, we'd be happy to try and help get you through it but we aren't familiar enough with those environments to provide a tutorial. Arlolra (talk) 19:48, 17 July 2019 (UTC)
The most basic things
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
I'm searching for a program that just takes plain Wikicode (I know how to code with it) and converts it to simple html, without the complicated things of hosting a wiki on my computer or things like that.
All of that offline, on a simple computer, installing as fewer things as possible (If I can, just make everything to install hold in a simple folder or USB key), with quite low programming skills.
I wonder if Parsoid fulfils these criteria (I couldn't get a lot of informations from the page).
Thank you for any answer! Julio974fr (talk) 17:08, 13 September 2018 (UTC)
- That somewhat depends on your definition of "offline".
- Parsoid's bin/parse.js has a flag --offline that will render your html without making any http requests, but you wouldn't be able to, for example, expand templates and fetch image info, since it requires access to a MediaWiki API for that kind of state.
- If your MediaWiki API is local to your host, you can --configure Parsoid to use that and it won't make any external requests. Arlolra (talk) 17:28, 13 September 2018 (UTC)
- I don't need to "host a wiki", but just to be able to simply convert wikicode text to html text. I forgot to clarify that. Is that still possible? Or is there another program that allows me to simply convert wikicode to html? Julio974fr (talk) 19:52, 13 September 2018 (UTC)
- Then the --offline option from above should be fine Arlolra (talk) 20:01, 13 September 2018 (UTC)
- And how should I use it? I remind that I'm a novice in cmd and github-related things Julio974fr (talk) 20:04, 13 September 2018 (UTC)
- See https://www.mediawiki.org/wiki/Parsoid#Converting_simple_wikitext and use the --offline flag Arlolra (talk) 20:33, 13 September 2018 (UTC)
- Is there a way to :
- 1) Give the link to a file with the wikicode, so it converts the entire things and output another file with the html?
- 2) Install this without Git and Nodejs (or, at least, to install both of these things in a single folder with nothing out of that)? Julio974fr (talk) 20:39, 13 September 2018 (UTC)
- --inputfile for the way in, output goes to stdout which you can pipe to a file
- See --help
- Node.js is required Arlolra (talk) 20:55, 13 September 2018 (UTC)
- Ok, I'll try it this weekend! Julio974fr (talk) 21:04, 13 September 2018 (UTC)
Issue starting parsoid
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hi Everyone.
Just further to this thread Talk:Parsoid/2018#h-installing_on_machine_that_is_not_internet_facing-2018-05-04T11:46:00.000Z, since that thread I have moved the Wiki to a new server, hence the reason for the delay in coming back to this.
I have done what was suggested and downloaded the deployment version of Parsoid and have installed node.js onto the server. I have tried to run
node bin\server.js
From the parsoid directory, but I get the error:
D:\wamp64\www\node_modules\parsoid>node -v
v8.12.0
D:\wamp64\www\node_modules\parsoid>node bin\server.js
module.js:550
throw err;
^
Error: Cannot find module 'service-runner'
at Function.Module._resolveFilename (module.js:548:15)
at Function.Module._load (module.js:475:25)
at Module.require (module.js:597:17)
at require (internal/module.js:11:18)
at Object.<anonymous> (D:\wamp64\www\node_modules\parsoid\bin\server.js:5:21
)
at Module._compile (module.js:653:30)
at Object.Module._extensions..js (module.js:664:10)
at Module.load (module.js:566:32)
at tryModuleLoad (module.js:506:12)
at Function.Module._load (module.js:498:3)
My LocalSettings.php looks like this:
wfLoadExtension( 'VisualEditor' );
//Enable by default for everybody
$wgDefaultUserOptions['visualeditor-enable'] = 1;
$wgVirtualRestConfig['modules']['parsoid'] = array(
// URL to the Parsoid instance
// Use port 8142 if you use the Debian package
'url' => 'http://domain.com:8000',
);
And my config.yamb looks like this:
mwApis:
- # This is the only required parameter,
# the URL of you MediaWiki API endpoint.
uri: 'http://domain.com/api.php'
# The "domain" is used for communication with Visual Editor
# and RESTBase. It defaults to the hostname portion of
# the `uri` property above, but you can manually set it
# to an arbitrary string. It must match the "domain" set
# in $wgVirtualRestConfig.
# domain: 'localhost' # optional
# To specify a proxy (or proxy headers) specific to this prefix
# (which overrides defaultAPIProxyURI). Alternatively, set `proxy`
# to `null` to override and force no proxying when a default proxy
# has been set.
#proxy:
# uri: 'http://my.proxy:1234/'
# headers: # optional
# 'X-Forwarded-Proto': 'https'
# See below, defaults to true.
#strictSSL: false
I have localsettings.js commented out at the moment, but either way it still doesn't seem to want to work.
I'm not sure what I'm doing wrong.
Any help is appreciated. Squeak24 (talk) 07:49, 18 September 2018 (UTC)
- What's the path the deploy repo you downloaded? You should be running the command from the root of that directory. Arlolra (talk) 16:38, 18 September 2018 (UTC)
- I have tried to have the deploy repo in the www directory, I changed the directory command prompt to that directory. I also put it in the Users AppData but still nothing. I have tried nodejs as well but that comes back with nothing.
- I am using a server that is not connected to the Internet, it is connected to the internal network without Internet access.
- Any help is appreciated. Squeak24 (talk) 01:11, 19 September 2018 (UTC)
- OK, I found out what the issue was, I downloaded the wrong version. I have it working now. Just need to get restBase installed now. 210.50.246.156 (talk) 06:40, 19 September 2018 (UTC)
problem with abbrev
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hello. i was following this step : Parsoid/Setup#Windows
and I'm struggling with installation.
I already tried :
- npm install -g abbrev@1.0.9
- npm install -g abbrev
- npm cache clean
- npm cache verify
- npm install parsoid --no-optional
- npm install --no-optional
and also..
- delete package-lock.jspn and reinstall
and...
- i couldn't find folder '.staging'
- my OS is Windows 10
Thank you! Kwmedaw1 (talk) 03:24, 19 September 2018 (UTC)
- Not really sure, but it looks like an npm issue more than anything.
- Google pointed me to https://foundation.zurb.com/forum/posts/57149-problem-using-npm-install-for-sass-foundation-cli which says "I found that there was a system variable that needed to be changed to prevent a Windows limit on length of file names and directory depth" Arlolra (talk) 01:05, 19 October 2018 (UTC)
Repo not signed error
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Getting this error when trying to do sudo apt-add-repository on Ubuntu 18.04, I swear it was working the other day.
W: GPG error: http://webmin.mirror.somersettechsolutions.co.uk/repository sarge Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D97A3AE911F63C51
E: The repository 'http://webmin.mirror.somersettechsolutions.co.uk/repository sarge Release' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: GPG error: http://download.webmin.com/download/repository sarge Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D97A3AE911F63C51
E: The repository 'http://download.webmin.com/download/repository sarge Release' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details. Smurfy (talk) 23:13, 21 September 2018 (UTC)
The Parsoid Guide needs updating and better formatting
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hi, I'm new to using Mediawiki but I just wanted to comment and say that I think the Parsoid guide is poorly written and needs some serious improvements. It's constantly sidetracked by notes on obsolete options, or alternative installation issues etc, which results in a very confusing stream of information to parse.
I was unable to install Parsoid correctly following the official guide but I found this one much easier to follow: https://www.howtoforge.com/tutorial/how-to-install-visualeditor-for-mediawiki-on-centos-7/
While the one linked is only for a specific OS and server type, I think it is a better example of how a Parsoid installation tutorial should be structured. The current one is very muddy and the structure of it is not consistent, at least to the eyes of a newbie like me. I am a newbie, but I think I have a decent understanding of technical information writing and the current shape of the article is not a good example of that. AslanFrench (talk) 21:11, 18 October 2018 (UTC)
- I'm sorry for the assessment of the documentation. It is community maintained so there's an opportunity for you to contribute improvements, if possible.
- Setting up Parsoid has been a thorn in many a MediaWiki developers side and is one motivating factor in porting Parsoid from JavaScript to PHP, to be included in core.
- Hopefully that will ease the burden of many peoples' setup moving forward.
- I appreciate the feedback. Arlolra (talk) 19:44, 17 July 2019 (UTC)
- Hi @Arlolra is there a chance you could tell me when approximately the port will finish? I know it's very difficult to say, but if you had to take a wild guess, would you say it's going to be like ~6 months or more like 2 years? Thanks MavropaliasG (talk) 16:01, 27 November 2019 (UTC)
- The port is currently in process of being deployed to WMF's production cluster so, for all extents and purposes, it's done. Arlolra (talk) 19:35, 27 November 2019 (UTC)
- I think that is wonderful news. Is there a good place to follow along with updates on its development? D8sychain (talk) 18:28, 21 December 2019 (UTC)
- https://www.mediawiki.org/wiki/Parsing/Notes/Moving_Parsoid_Into_Core/Porting
- https://www.mediawiki.org/wiki/Parsoid/PHP Arlolra (talk) 16:10, 13 April 2020 (UTC)
Trouble configuring Parsoid with VE, any help much appreciated.
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hi. I'm a designer learning how to develop, so I'm not the best at backend stuff but I am decently technically minded. I am having a bit of trouble getting my installation of Mediwiki with the visual editor extension working.
The weird thing is that it wasn't working and then I made several changes to my config files following the parsoid setup guide and then it was working! And then I refreshed the page to see if my changes had properly kept and they had. BUT! then as soon as I tried to hit edit again I started getting the same error message back, and I can't get it to stop:
Error loading data from server: apierror-visualeditor-docserver-http-error: (curl error: 7) Couldn't connect to server. Would you like to retry?
I don't know how to get it stop doing that. Any suggestions? AslanFrench (talk) 21:56, 18 October 2018 (UTC)
- Can you confirm that Parsoid itself is running? Assuming you've configured it use port 8000, curl http://localhost:8000 or visiting that url with your browser should display the welcome page. Arlolra (talk) 00:46, 19 October 2018 (UTC)
- @Arlolra Thank you for responding. from what I can tell from using the curl stuff, Parsoid is not running. I get a similar curl 7 error. I have collected a huge amount of troubleshooting and log information on the discourse forums here: https://discourse-mediawiki.wmflabs.org/t/error-loading-data-from-server-apierror-visualeditor-docserver-http-error-curl-error-7-couldnt-connect-to-server/865 AslanFrench (talk) 01:08, 19 October 2018 (UTC)
- In the first set of logs there, it says "ready on :8142", so not 8000
- In the second, it says "Error: bind EADDRINUSE null:8000 ..." which means you were trying to spin it up on 8000 but something else is using that port. Maybe another Parsoid instance or something else on your server.
- The second time you were invoking bin/server.js directly, which would default to 8000.
- The first time, it seems like you're pasting the logs from a server where you've installed Parsoid through apt-get and the service defaulted to 8142.
- My guess is that if you try, curl http://localhost:8142 you'll get the welcome page Arlolra (talk) 01:16, 19 October 2018 (UTC)
- @Arlolra Yes! Indeed it does!
- So what does that mean? Do I just change all my config files to 8142? I tried that before and that didn't seem to work AslanFrench (talk) 02:12, 19 October 2018 (UTC)
- Okay I changed my thing to 8142 in my localsettings.php and this is what I got:
david@lovelace:/usr/lib/parsoid/src/bin$ service nginx restart && service parsoid restart && node server.jsgo{"name":"parsoid","hostname":"lovelace","pid":32335,"level":30,"levelPath":"info/service-runner","msg":"master(32335) initializing 4 workers","time":"2018-10-19T02:14:42.715Z","v":0}{"name":"../src/lib/index.js","hostname":"lovelace","pid":32359,"level":30,"levelPath":"info","msg":"loading ...","time":"2018-10-19T02:14:44.411Z","v":0}{"name":"../src/lib/index.js","hostname":"lovelace","pid":32359,"level":30,"levelPath":"info","msg":"ready on :8000","time":"2018-10-19T02:14:44.526Z","v":0}{"name":"../src/lib/index.js","hostname":"lovelace","pid":32370,"level":30,"levelPath":"info","msg":"loading ...","time":"2018-10-19T02:14:45.556Z","v":0}{"name":"../src/lib/index.js","hostname":"lovelace","pid":32370,"level":30,"levelPath":"info","msg":"ready on :8000","time":"2018-10-19T02:14:45.593Z","v":0}{"name":"../src/lib/index.js","hostname":"lovelace","pid":32380,"level":30,"levelPath":"info","msg":"loading ...","time":"2018-10-19T02:14:46.637Z","v":0}{"name":"../src/lib/index.js","hostname":"lovelace","pid":32380,"level":30,"levelPath":"info","msg":"ready on :8000","time":"2018-10-19T02:14:46.675Z","v":0}{"name":"../src/lib/index.js","hostname":"lovelace","pid":32412,"level":30,"levelPath":"info","msg":"loading ...","time":"2018-10-19T02:14:47.708Z","v":0}{"name":"../src/lib/index.js","hostname":"lovelace","pid":32412,"level":30,"levelPath":"info","msg":"ready on :8000","time":"2018-10-19T02:14:47.746Z","v":0}{"name":"parsoid","hostname":"lovelace","pid":32335,"level":40,"levelPath":"warn/service-runner","msg":"startup finished","time":"2018-10-19T02:14:47.747Z","v":0}AslanFrench (talk) 02:16, 19 October 2018 (UTC)- It looks like it's still defaulting to 8000. I changed it in my LocalSetttings.php though, and I don't see anywhere to change it in my config.yaml file in either of the parsoid installs? Is there another config file I'm missing? AslanFrench (talk) 02:19, 19 October 2018 (UTC)
- Sorry for so many double posts. I also tried curl localhost:8000 and that gave me the welcome page too?
- Could it have something to do with my virtual hosts? As in I can access parsoid through 8000 or 8142 but I can't access them though my wiki.example.com subdomains? AslanFrench (talk) 02:21, 19 October 2018 (UTC)
- When you install Parsoid via apt-get, it installs a service that gets run at boot, etc. via systemv init, upstart, or whathaveyou. That one is running on 8142.
- Then, when you invoke bin/server.js you're starting a second service on 8000.
- Basically, it sounds like you're now running two separate instances of Parsoid, that're likely not using the same config.yaml file. Arlolra (talk) 03:00, 19 October 2018 (UTC)
- @Arlolra Okay yeah so what would be the best way for me to get it to work?
- Should I change LocalSettings.php to 8142?
- Should I change the apt-get install to 800? How would I do that?
- I'm going to try rebooting the machine and see what that gets me. But I think the 8000 might be taken up by my NextCloud server. NextCloud, Mediawiki, and Parsoid are all installed on my local home desktop machine. AslanFrench (talk) 04:15, 19 October 2018 (UTC)
- I rebooted and ran curl 8000 and got the correct response and when I ran curl 8142 I got the error code. I checked and my LocalSettings.php was set to 8142 so I set it to 8000 and rebooted again and I got the same result. 8000 connects. 8142 doesn't. But when trying to use the visual editor it does not work and I get the same no connection error code. AslanFrench (talk) 05:42, 19 October 2018 (UTC)
- I've also got a netstat out put here:
Active Internet connections (w/o servers)Proto Recv-Q Send-Q Local Address Foreign Address Statetcp 0 0 lovelace:37298 US-NJC-ANX-R003.te:5938 ESTABLISHEDtcp 0 0 lovelace:49784 104.16.0.35:https TIME_WAITtcp 0 0 localhost:5939 localhost:40324 ESTABLISHEDtcp 0 0 lovelace:https _gateway:12964 ESTABLISHEDtcp 0 0 lovelace:50466 stackoverflow.com:https ESTABLISHEDtcp 0 0 lovelace:38370 a104-112-72-3.dep:https ESTABLISHEDtcp 0 0 lovelace:53858 dfw25s12-in-f46.1:https TIME_WAITtcp 0 0 localhost:58356 localhost:8000 TIME_WAITtcp 32 0 lovelace:38350 a104-112-72-3.dep:https CLOSE_WAITtcp 32 0 lovelace:38800 a172-231-5-110.de:https CLOSE_WAITtcp 0 0 lovelace:56640 atl14s07-in-f138.:https TIME_WAITtcp 0 0 lovelace:50644 stackoverflow.com:https ESTABLISHEDtcp 0 0 lovelace:https _gateway:41716 ESTABLISHEDtcp 0 0 lovelace:47446 177.143.198.104.bc:http TIME_WAITtcp 0 0 lovelace:42148 do-23.lastpass.co:https ESTABLISHEDtcp 0 0 lovelace:41716 GFiberRouter:https ESTABLISHEDtcp 1 0 lovelace:60916 server-54-230-4-3:https CLOSE_WAITtcp 0 0 lovelace:51156 ec2-35-162-209-90:https ESTABLISHEDtcp 0 0 lovelace:47570 dfw06s49-in-f14.1:https TIME_WAITtcp 0 0 lovelace:44030 dfw25s13-in-f1.1e:https TIME_WAITtcp 0 0 lovelace:60254 dfw25s16-in-f132.:https TIME_WAITtcp 0 0 lovelace:33496 192.0.73.2:https TIME_WAITtcp 0 0 localhost:40324 localhost:5939 ESTABLISHEDtcp 0 0 lovelace:56576 ec2-54-89-31-218.:https ESTABLISHEDtcp 0 0 lovelace:https _gateway:12953 TIME_WAITtcp 0 0 lovelace:https _gateway:12963 TIME_WAITtcp 0 0 lovelace:50642 stackoverflow.com:https ESTABLISHEDsctp ip6-localhost:3478 LISTENsctp lovelace:3478 LISTENsctp lovelace:3478 LISTENsctp localhost:3478 LISTENsctp ip6-localhost:3479 LISTENsctp lovelace:3479 LISTENsctp lovelace:3479 LISTENsctp localhost:3479 LISTENsctp ip6-localhost:5349 LISTENsctp lovelace:5349 LISTENsctp lovelace:5349 LISTENsctp localhost:5349 LISTENsctp ip6-localhost:5350 LISTENsctp lovelace:5350 LISTENsctp lovelace:5350 LISTENsctp localhost:5350 LISTENActive UNIX domain sockets (w/o servers)Proto RefCnt Flags Type State I-Node Pathunix 2 [ ] DGRAM 45913 /run/user/1000/systemd/notifyunix 7 [ ] DGRAM 54582 @nvidia0230bd29@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@unix 2 [ ] DGRAM 45490 /run/wpa_supplicant/wlx2016d8371d77unix 3 [ ] DGRAM 2670 /run/systemd/notifyunix 9 [ ] DGRAM 2700 /run/systemd/journal/socketunix 27 [ ] DGRAM 2713 /run/systemd/journal/dev-logunix 2 [ ] DGRAM 2715 /run/systemd/journal/syslogunix 3 [ ] SEQPACKET CONNECTED 202547 @00015unix 3 [ ] STREAM CONNECTED 24537 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 191831 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 26063unix 3 [ ] STREAM CONNECTED 86540 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 75221 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 67633 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 59735 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 54536unix 3 [ ] STREAM CONNECTED 42683unix 3 [ ] STREAM CONNECTED 78336unix 3 [ ] STREAM CONNECTED 67738 /run/systemd/journal/stdoutunix 2 [ ] DGRAM 57928unix 3 [ ] STREAM CONNECTED 35717unix 3 [ ] STREAM CONNECTED 71328 @/tmp/dbus-24cwLSLIEjunix 3 [ ] STREAM CONNECTED 67988unix 3 [ ] STREAM CONNECTED 39281 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 68268 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 61245unix 3 [ ] STREAM CONNECTED 74435 /run/user/1000/busunix 2 [ ] DGRAM 68745unix 3 [ ] STREAM CONNECTED 67646 @/tmp/.ICE-unix/2219unix 3 [ ] STREAM CONNECTED 54765unix 3 [ ] STREAM CONNECTED 45965 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 83144unix 3 [ ] STREAM CONNECTED 71500 @/tmp/dbus-24cwLSLIEjunix 3 [ ] STREAM CONNECTED 70346unix 3 [ ] STREAM CONNECTED 69647 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 62222 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 67584unix 3 [ ] STREAM CONNECTED 27681 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 215311 @/dbus-vfs-daemon/socket-nn6NFxVcunix 3 [ ] STREAM CONNECTED 70914 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 67789 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 67423 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 57540unix 3 [ ] STREAM CONNECTED 33025unix 3 [ ] STREAM CONNECTED 79081unix 3 [ ] STREAM CONNECTED 63142unix 2 [ ] DGRAM 21481unix 3 [ ] STREAM CONNECTED 214557unix 3 [ ] STREAM CONNECTED 201627unix 3 [ ] STREAM CONNECTED 83143unix 3 [ ] STREAM CONNECTED 70191 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 69643unix 3 [ ] STREAM CONNECTED 62200 /run/systemd/journal/stdoutunix 3 [ ] DGRAM 45914unix 3 [ ] STREAM CONNECTED 202678unix 2 [ ] DGRAM 68976unix 3 [ ] STREAM CONNECTED 67989 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 190676unix 3 [ ] STREAM CONNECTED 84607unix 3 [ ] STREAM CONNECTED 86062unix 3 [ ] STREAM CONNECTED 62450 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 57545 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 46056unix 3 [ ] STREAM CONNECTED 26301unix 3 [ ] STREAM CONNECTED 82439 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 69646unix 3 [ ] STREAM CONNECTED 67628unix 3 [ ] STREAM CONNECTED 57564 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 29184unix 3 [ ] STREAM CONNECTED 78337 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 69991unix 3 [ ] STREAM CONNECTED 61234unix 3 [ ] STREAM CONNECTED 84604unix 3 [ ] STREAM CONNECTED 62451 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 27685 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 21483unix 3 [ ] STREAM CONNECTED 23058 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 202965unix 3 [ ] STREAM CONNECTED 68358 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 69654 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 67737unix 3 [ ] STREAM CONNECTED 67554unix 3 [ ] STREAM CONNECTED 191830unix 3 [ ] STREAM CONNECTED 84009 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 61236unix 3 [ ] STREAM CONNECTED 190677 @/tmp/dbus-24cwLSLIEjunix 3 [ ] STREAM CONNECTED 86545 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 63223unix 2 [ ] DGRAM 54743unix 3 [ ] STREAM CONNECTED 54594 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 30381 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 24999unix 3 [ ] STREAM CONNECTED 70680 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 67787unix 3 [ ] STREAM CONNECTED 67763unix 3 [ ] STREAM CONNECTED 67669unix 3 [ ] STREAM CONNECTED 67991 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 67555 /run/systemd/journal/stdoutunix 2 [ ] DGRAM 190683unix 3 [ ] STREAM CONNECTED 61235 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 27683 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 189859 @/tmp/.X11-unix/X0unix 3 [ ] STREAM CONNECTED 67670 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 83140unix 3 [ ] STREAM CONNECTED 71499unix 3 [ ] STREAM CONNECTED 69642 /run/systemd/journal/stdoutunix 2 [ ] DGRAM 67582unix 3 [ ] STREAM CONNECTED 67608unix 3 [ ] STREAM CONNECTED 35716unix 3 [ ] STREAM CONNECTED 21455unix 3 [ ] STREAM CONNECTED 214553unix 3 [ ] STREAM CONNECTED 71329unix 3 [ ] STREAM CONNECTED 88097 @/tmp/.X11-unix/X0unix 3 [ ] STREAM CONNECTED 79086unix 3 [ ] STREAM CONNECTED 71408 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 70909unix 3 [ ] STREAM CONNECTED 63376unix 3 [ ] STREAM CONNECTED 60250 /run/user/1000/busunix 2 [ ] STREAM CONNECTED 28399unix 3 [ ] STREAM CONNECTED 30956unix 3 [ ] STREAM CONNECTED 23149 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 79934unix 3 [ ] STREAM CONNECTED 70337 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 62221 /run/systemd/journal/stdoutunix 3 [ ] DGRAM 45915unix 3 [ ] STREAM CONNECTED 214555unix 3 [ ] STREAM CONNECTED 202679unix 3 [ ] STREAM CONNECTED 39122 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 80884unix 3 [ ] STREAM CONNECTED 69655unix 3 [ ] STREAM CONNECTED 86544 @/tmp/dbus-24cwLSLIEjunix 3 [ ] STREAM CONNECTED 67900unix 3 [ ] STREAM CONNECTED 27684 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 202964unix 3 [ ] SEQPACKET CONNECTED 83150unix 3 [ ] STREAM CONNECTED 70336unix 3 [ ] STREAM CONNECTED 67713unix 3 [ ] STREAM CONNECTED 63137 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 71354unix 3 [ ] STREAM CONNECTED 70898 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 70895 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 74464unix 3 [ ] STREAM CONNECTED 69649 @/tmp/.X11-unix/X0unix 3 [ ] STREAM CONNECTED 70913 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 63183unix 3 [ ] STREAM CONNECTED 58305unix 3 [ ] STREAM CONNECTED 58178unix 3 [ ] STREAM CONNECTED 214558 @/dbus-vfs-daemon/socket-c87r3A9tunix 3 [ ] STREAM CONNECTED 80563unix 3 [ ] STREAM CONNECTED 69653 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 62246 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 57569 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 201645 @/tmp/.X11-unix/X0unix 3 [ ] STREAM CONNECTED 68902 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 71327unix 3 [ ] STREAM CONNECTED 67990unix 3 [ ] STREAM CONNECTED 67526unix 3 [ ] STREAM CONNECTED 24761unix 3 [ ] STREAM CONNECTED 83266unix 2 [ ] DGRAM 79010unix 3 [ ] STREAM CONNECTED 67993unix 3 [ ] STREAM CONNECTED 69652 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 67741unix 3 [ ] STREAM CONNECTED 60631 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 84609unix 3 [ ] STREAM CONNECTED 57260 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 33278unix 3 [ ] STREAM CONNECTED 213194unix 3 [ ] STREAM CONNECTED 83139unix 3 [ ] STREAM CONNECTED 70347 @/tmp/.X11-unix/X0unix 3 [ ] STREAM CONNECTED 67790unix 3 [ ] STREAM CONNECTED 69641unix 3 [ ] STREAM CONNECTED 67714unix 3 [ ] STREAM CONNECTED 58519unix 3 [ ] STREAM CONNECTED 42631 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 27877unix 2 [ ] DGRAM 2730unix 3 [ ] STREAM CONNECTED 71352unix 3 [ ] STREAM CONNECTED 67553unix 3 [ ] STREAM CONNECTED 201632unix 3 [ ] STREAM CONNECTED 68297unix 3 [ ] STREAM CONNECTED 70896 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 63061 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 57948unix 3 [ ] STREAM CONNECTED 63220unix 3 [ ] STREAM CONNECTED 61251 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 67430 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 45964 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 21494unix 3 [ ] STREAM CONNECTED 75641 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 63476 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 62201 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 25449 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 71353 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 70897unix 3 [ ] STREAM CONNECTED 70894unix 3 [ ] SEQPACKET CONNECTED 80889unix 3 [ ] STREAM CONNECTED 67994 @/tmp/.X11-unix/X0unix 3 [ ] STREAM CONNECTED 86541 /run/systemd/journal/stdoutunix 2 [ ] DGRAM 68674unix 3 [ ] STREAM CONNECTED 54934unix 2 [ ] DGRAM 21488unix 3 [ ] STREAM CONNECTED 63475unix 3 [ ] STREAM CONNECTED 67668unix 3 [ ] STREAM CONNECTED 56855 /run/acpid.socketunix 3 [ ] STREAM CONNECTED 217138 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 201633unix 3 [ ] STREAM CONNECTED 68267unix 3 [ ] STREAM CONNECTED 61244unix 3 [ ] STREAM CONNECTED 84605unix 3 [ ] STREAM CONNECTED 75060unix 3 [ ] STREAM CONNECTED 70910unix 3 [ ] STREAM CONNECTED 68650 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 59475unix 3 [ ] STREAM CONNECTED 79924unix 3 [ ] STREAM CONNECTED 69644 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 62245 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 42630 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 28271 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 61908 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 56163 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 86063unix 3 [ ] STREAM CONNECTED 78361 /var/run/dbus/system_bus_socketunix 2 [ ] DGRAM 68747unix 3 [ ] STREAM CONNECTED 68042 @/tmp/.X11-unix/X0unix 3 [ ] STREAM CONNECTED 67899unix 3 [ ] STREAM CONNECTED 61830 /run/user/1000/pulse/nativeunix 2 [ ] DGRAM 49490unix 3 [ ] STREAM CONNECTED 210695 @/dbus-vfs-daemon/socket-7cRE35Qyunix 3 [ ] SEQPACKET CONNECTED 83151unix 3 [ ] STREAM CONNECTED 69708unix 3 [ ] STREAM CONNECTED 62208 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 67629unix 3 [ ] STREAM CONNECTED 54583unix 2 [ ] DGRAM 28270unix 2 [ ] DGRAM 24809unix 3 [ ] STREAM CONNECTED 199540unix 3 [ ] STREAM CONNECTED 63077 /run/user/1000/pulse/nativeunix 3 [ ] STREAM CONNECTED 40000unix 3 [ ] SEQPACKET CONNECTED 202548unix 3 [ ] STREAM CONNECTED 61230unix 3 [ ] STREAM CONNECTED 55978 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 190674unix 3 [ ] STREAM CONNECTED 84610unix 2 [ ] DGRAM 68744unix 3 [ ] STREAM CONNECTED 67637 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 60414 @/tmp/.X11-unix/X0unix 3 [ ] STREAM CONNECTED 42684 @/tmp/dbus-KUwbgiPSunix 3 [ ] STREAM CONNECTED 26383unix 3 [ ] STREAM CONNECTED 201628unix 3 [ ] STREAM CONNECTED 74687 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 68643unix 3 [ ] STREAM CONNECTED 62145 /run/systemd/journal/stdoutunix 2 [ ] DGRAM 47088unix 3 [ ] STREAM CONNECTED 201639unix 3 [ ] STREAM CONNECTED 69041unix 3 [ ] STREAM CONNECTED 57907unix 3 [ ] STREAM CONNECTED 32532unix 3 [ ] STREAM CONNECTED 62343 /run/user/1000/busunix 3 [ ] DGRAM 2671unix 3 [ ] STREAM CONNECTED 71554unix 2 [ ] DGRAM 70093unix 3 [ ] STREAM CONNECTED 68084unix 3 [ ] STREAM CONNECTED 57925unix 3 [ ] STREAM CONNECTED 71271unix 3 [ ] STREAM CONNECTED 35978unix 3 [ ] STREAM CONNECTED 202949unix 3 [ ] STREAM CONNECTED 71462 @/tmp/dbus-24cwLSLIEjunix 3 [ ] STREAM CONNECTED 68269 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 57898unix 2 [ ] DGRAM 28411unix 3 [ ] STREAM CONNECTED 70900unix 2 [ ] DGRAM 58045unix 3 [ ] STREAM CONNECTED 60684unix 3 [ ] STREAM CONNECTED 57306 /run/systemd/journal/stdoutunix 3 [ ] DGRAM 22739unix 3 [ ] STREAM CONNECTED 202936unix 3 [ ] STREAM CONNECTED 202851unix 3 [ ] STREAM CONNECTED 71245unix 3 [ ] STREAM CONNECTED 61578unix 3 [ ] STREAM CONNECTED 201643unix 3 [ ] STREAM CONNECTED 78318unix 3 [ ] STREAM CONNECTED 68111unix 3 [ ] STREAM CONNECTED 67992unix 3 [ ] STREAM CONNECTED 62315 @/tmp/dbus-24cwLSLIEjunix 3 [ ] STREAM CONNECTED 71150unix 3 [ ] STREAM CONNECTED 56990unix 3 [ ] STREAM CONNECTED 215431unix 3 [ ] STREAM CONNECTED 199549unix 3 [ ] STREAM CONNECTED 46005unix 2 [ ] DGRAM 27664unix 3 [ ] STREAM CONNECTED 201640unix 3 [ ] STREAM CONNECTED 202579unix 3 [ ] STREAM CONNECTED 83046 @/tmp/dbus-DOriWtQmunix 3 [ ] STREAM CONNECTED 70190unix 3 [ ] STREAM CONNECTED 70146 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 63445 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 60190 /var/run/docker/containerd/docker-containerd.sockunix 3 [ ] STREAM CONNECTED 62256 @/tmp/dbus-24cwLSLIEjunix 2 [ ] DGRAM 42698unix 3 [ ] STREAM CONNECTED 80891unix 3 [ ] STREAM CONNECTED 71432 @/tmp/.X11-unix/X0unix 3 [ ] STREAM CONNECTED 71198 @/tmp/.X11-unix/X0unix 3 [ ] STREAM CONNECTED 20854 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 201641 @/tmp/.X11-unix/X0unix 2 [ ] DGRAM 68901unix 3 [ ] STREAM CONNECTED 70198 /run/systemd/journal/stdoutunix 2 [ ] DGRAM 63110unix 3 [ ] STREAM CONNECTED 59051unix 2 [ ] DGRAM 46065unix 3 [ ] STREAM CONNECTED 202703 /tmp/vscode-ipc-7812149c-9c63-4724-b869-063c6b2cb7c0.sockunix 3 [ ] STREAM CONNECTED 62249 @/tmp/.X11-unix/X0unix 3 [ ] STREAM CONNECTED 49465unix 3 [ ] STREAM CONNECTED 68298 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 62338unix 3 [ ] STREAM CONNECTED 74420 @/tmp/dbus-DOriWtQmunix 3 [ ] STREAM CONNECTED 71555 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 59703unix 3 [ ] STREAM CONNECTED 202930unix 3 [ ] STREAM CONNECTED 79082 /run/user/1000/busunix 3 [ ] DGRAM 21309unix 3 [ ] STREAM CONNECTED 199539 @/tmp/.X11-unix/X0unix 3 [ ] STREAM CONNECTED 83045unix 3 [ ] STREAM CONNECTED 70690 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 63440unix 3 [ ] STREAM CONNECTED 60712unix 3 [ ] STREAM CONNECTED 27682 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 62257unix 3 [ ] STREAM CONNECTED 60683unix 3 [ ] DGRAM 2672unix 3 [ ] STREAM CONNECTED 74990unix 3 [ ] STREAM CONNECTED 56991unix 3 [ ] STREAM CONNECTED 202939unix 3 [ ] STREAM CONNECTED 57627unix 3 [ ] STREAM CONNECTED 34909 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 70143unix 2 [ ] STREAM CONNECTED 69721unix 3 [ ] STREAM CONNECTED 60714unix 3 [ ] STREAM CONNECTED 28647 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 62314unix 3 [ ] STREAM CONNECTED 55611 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 202759 @/tmp/.X11-unix/X0unix 3 [ ] STREAM CONNECTED 80893unix 3 [ ] STREAM CONNECTED 71318 @/tmp/.X11-unix/X0unix 3 [ ] STREAM CONNECTED 68075 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 56992 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 216417 @/tmp/dbus-24cwLSLIEjunix 3 [ ] STREAM CONNECTED 202932unix 3 [ ] STREAM CONNECTED 202762unix 3 [ ] STREAM CONNECTED 63073unix 3 [ ] STREAM CONNECTED 56152 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 55059unix 3 [ ] STREAM CONNECTED 202578unix 3 [ ] STREAM CONNECTED 199534 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 77798 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 63470 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 60529 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 63472 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 68085 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 46069 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 202696 @/tmp/dbus-DOriWtQmunix 3 [ ] STREAM CONNECTED 202929unix 3 [ ] STREAM CONNECTED 202761unix 3 [ ] STREAM CONNECTED 60710 @/tmp/.X11-unix/X0unix 3 [ ] STREAM CONNECTED 83153unix 3 [ ] STREAM CONNECTED 70144unix 3 [ ] STREAM CONNECTED 69718unix 3 [ ] STREAM CONNECTED 59846 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 62341 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 201631unix 3 [ ] STREAM CONNECTED 217157 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 200699unix 3 [ ] STREAM CONNECTED 78360unix 3 [ ] STREAM CONNECTED 71244unix 3 [ ] STREAM CONNECTED 59631unix 3 [ ] STREAM CONNECTED 23157 /run/systemd/journal/stdoutunix 2 [ ] DGRAM 21306unix 3 [ ] STREAM CONNECTED 83154unix 3 [ ] STREAM CONNECTED 74388unix 3 [ ] STREAM CONNECTED 67953 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 63467unix 3 [ ] SEQPACKET CONNECTED 70419unix 3 [ ] STREAM CONNECTED 69978 @/tmp/dbus-24cwLSLIEjunix 3 [ ] STREAM CONNECTED 212449 @/dbus-vfs-daemon/socket-gZFstJjnunix 3 [ ] STREAM CONNECTED 71431unix 3 [ ] STREAM CONNECTED 71162unix 3 [ ] STREAM CONNECTED 57926 /var/run/dbus/system_bus_socketunix 3 [ ] DGRAM 22740unix 3 [ ] STREAM CONNECTED 202931unix 3 [ ] STREAM CONNECTED 200698unix 3 [ ] STREAM CONNECTED 70382 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 46066unix 3 [ ] DGRAM 21308unix 3 [ ] STREAM CONNECTED 83155unix 3 [ ] STREAM CONNECTED 70041unix 3 [ ] STREAM CONNECTED 63469unix 3 [ ] STREAM CONNECTED 57899unix 3 [ ] STREAM CONNECTED 21456unix 3 [ ] STREAM CONNECTED 67788 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 35019 /run/systemd/journal/stdoutunix 2 [ ] DGRAM 86546unix 3 [ ] STREAM CONNECTED 62456unix 3 [ ] STREAM CONNECTED 202938unix 3 [ ] STREAM CONNECTED 201680unix 3 [ ] STREAM CONNECTED 68186 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 61955unix 3 [ ] STREAM CONNECTED 58131 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 26711unix 3 [ ] STREAM CONNECTED 60528 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 57307 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 70349 @/tmp/.X11-unix/X0unix 3 [ ] STREAM CONNECTED 62339 /run/systemd/journal/stdoutunix 3 [ ] SEQPACKET CONNECTED 80890unix 3 [ ] STREAM CONNECTED 71217 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 68714 @/tmp/.ICE-unix/2219unix 3 [ ] STREAM CONNECTED 56108unix 3 [ ] STREAM CONNECTED 202935unix 3 [ ] STREAM CONNECTED 69473unix 3 [ ] STREAM CONNECTED 71490unix 3 [ ] STREAM CONNECTED 61249 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 59255unix 3 [ ] STREAM CONNECTED 46067unix 3 [ ] STREAM CONNECTED 23156 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 80635unix 3 [ ] STREAM CONNECTED 68156unix 3 [ ] STREAM CONNECTED 70145 /run/systemd/journal/stdoutunix 3 [ ] SEQPACKET CONNECTED 70418unix 3 [ ] STREAM CONNECTED 62340unix 3 [ ] STREAM CONNECTED 80894unix 3 [ ] STREAM CONNECTED 74421unix 3 [ ] STREAM CONNECTED 70250unix 3 [ ] STREAM CONNECTED 62368 @/tmp/.X11-unix/X0unix 3 [ ] STREAM CONNECTED 202933unix 3 [ ] STREAM CONNECTED 83568unix 3 [ ] STREAM CONNECTED 60415 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 69710unix 3 [ ] STREAM CONNECTED 63444unix 3 [ ] STREAM CONNECTED 62316unix 3 [ ] STREAM CONNECTED 181183unix 3 [ ] STREAM CONNECTED 71197unix 3 [ ] STREAM CONNECTED 202934unix 3 [ ] STREAM CONNECTED 68185 /run/systemd/journal/stdoutunix 2 [ ] STREAM CONNECTED 33262unix 3 [ ] STREAM CONNECTED 201630unix 3 [ ] STREAM CONNECTED 74387unix 3 [ ] STREAM CONNECTED 70042 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 63468 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 62520unix 3 [ ] STREAM CONNECTED 48822 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 62255unix 3 [ ] STREAM CONNECTED 36204unix 3 [ ] STREAM CONNECTED 210698unix 3 [ ] STREAM CONNECTED 181182unix 3 [ ] STREAM CONNECTED 22471unix 3 [ ] STREAM CONNECTED 215433unix 3 [ ] STREAM CONNECTED 199548unix 3 [ ] STREAM CONNECTED 70197 /run/systemd/journal/stdoutunix 3 [ ] DGRAM 21310unix 2 [ ] DGRAM 3774unix 3 [ ] STREAM CONNECTED 83152unix 3 [ ] STREAM CONNECTED 80634unix 3 [ ] STREAM CONNECTED 71436unix 3 [ ] STREAM CONNECTED 59054 @/tmp/dbus-24cwLSLIEjunix 3 [ ] STREAM CONNECTED 68258unix 3 [ ] STREAM CONNECTED 62342unix 3 [ ] STREAM CONNECTED 56668unix 2 [ ] DGRAM 71164unix 3 [ ] STREAM CONNECTED 61909 /run/systemd/journal/stdoutunix 2 [ ] DGRAM 191908unix 3 [ ] STREAM CONNECTED 71270unix 3 [ ] STREAM CONNECTED 33263unix 3 [ ] STREAM CONNECTED 189813unix 3 [ ] STREAM CONNECTED 80892unix 3 [ ] STREAM CONNECTED 75640 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 78324 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 68398 @/tmp/dbus-DOriWtQmunix 3 [ ] STREAM CONNECTED 21476unix 3 [ ] STREAM CONNECTED 202553 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 182907unix 3 [ ] STREAM CONNECTED 68900 /run/systemd/journal/stdoutunix 2 [ ] DGRAM 67977unix 3 [ ] STREAM CONNECTED 69663unix 3 [ ] STREAM CONNECTED 58818 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 236386unix 3 [ ] STREAM CONNECTED 202736unix 3 [ ] STREAM CONNECTED 71483 @/tmp/dbus-24cwLSLIEjunix 3 [ ] STREAM CONNECTED 71441unix 2 [ ] DGRAM 71423unix 3 [ ] STREAM CONNECTED 26629unix 3 [ ] STREAM CONNECTED 63413unix 3 [ ] STREAM CONNECTED 191613 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 83554unix 3 [ ] STREAM CONNECTED 68397unix 3 [ ] STREAM CONNECTED 68913 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 57532unix 3 [ ] STREAM CONNECTED 217160 @/tmp/.X11-unix/X0unix 2 [ ] DGRAM 190678unix 3 [ ] STREAM CONNECTED 182912unix 3 [ ] STREAM CONNECTED 70301unix 3 [ ] STREAM CONNECTED 67952unix 3 [ ] STREAM CONNECTED 69667 @/tmp/.X11-unix/X0unix 3 [ ] STREAM CONNECTED 60184unix 3 [ ] STREAM CONNECTED 47138unix 3 [ ] STREAM CONNECTED 236387unix 3 [ ] STREAM CONNECTED 199530unix 2 [ ] DGRAM 70429unix 3 [ ] STREAM CONNECTED 71482unix 3 [ ] STREAM CONNECTED 58826unix 3 [ ] STREAM CONNECTED 26983unix 3 [ ] STREAM CONNECTED 26886unix 3 [ ] STREAM CONNECTED 26547unix 3 [ ] STREAM CONNECTED 68264 @/tmp/.ICE-unix/2219unix 3 [ ] STREAM CONNECTED 54762 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 202686unix 3 [ ] STREAM CONNECTED 74683unix 3 [ ] STREAM CONNECTED 71357 @/tmp/.X11-unix/X0unix 3 [ ] STREAM CONNECTED 57514 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 69670unix 3 [ ] STREAM CONNECTED 60604unix 2 [ ] DGRAM 199531unix 3 [ ] STREAM CONNECTED 60100 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 57537unix 3 [ ] STREAM CONNECTED 87229 @/tmp/dbus-24cwLSLIEjunix 3 [ ] STREAM CONNECTED 63412unix 3 [ ] STREAM CONNECTED 210671unix 3 [ ] STREAM CONNECTED 80553 @/tmp/.ICE-unix/2219unix 3 [ ] STREAM CONNECTED 70316unix 3 [ ] STREAM CONNECTED 71355 /run/systemd/journal/stdoutunix 3 [ ] SEQPACKET CONNECTED 182918unix 3 [ ] STREAM CONNECTED 69011unix 3 [ ] STREAM CONNECTED 69685 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 67927unix 2 [ ] DGRAM 59011unix 3 [ ] STREAM CONNECTED 60605unix 3 [ ] STREAM CONNECTED 27688 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 27686 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 237244 /run/user/1000/pulse/nativeunix 3 [ ] STREAM CONNECTED 202867unix 3 [ ] STREAM CONNECTED 88226 @/tmp/dbus-DOriWtQmunix 3 [ ] STREAM CONNECTED 70428unix 2 [ ] DGRAM 217162unix 3 [ ] STREAM CONNECTED 190651 @/dbus-vfs-daemon/socket-Ap99CF3nunix 3 [ ] STREAM CONNECTED 83556unix 3 [ ] STREAM CONNECTED 75048unix 3 [ ] STREAM CONNECTED 71205unix 3 [ ] STREAM CONNECTED 67556 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 25077unix 3 [ ] STREAM CONNECTED 70689 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 67906 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 62372 @/tmp/dbus-24cwLSLIEjunix 3 [ ] STREAM CONNECTED 60131 /var/run/docker/containerd/docker-containerd.sockunix 3 [ ] STREAM CONNECTED 47139unix 3 [ ] STREAM CONNECTED 210669 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 202972 /run/user/1000/vscode-10a394bb-1.27.1-shared.sockunix 3 [ ] STREAM CONNECTED 88225unix 3 [ ] STREAM CONNECTED 85124unix 3 [ ] STREAM CONNECTED 68333 @/tmp/dbus-DOriWtQmunix 3 [ ] STREAM CONNECTED 58855 @/tmp/.ICE-unix/2219unix 3 [ ] STREAM CONNECTED 84363unix 3 [ ] STREAM CONNECTED 63066 @/tmp/dbus-24cwLSLIEjunix 2 [ ] DGRAM 55767unix 3 [ ] SEQPACKET CONNECTED 202544unix 3 [ ] STREAM CONNECTED 70334 /var/run/dbus/system_bus_socketunix 2 [ ] DGRAM 70915unix 2 [ ] DGRAM 61452unix 2 [ ] DGRAM 21470unix 3 [ ] STREAM CONNECTED 215434 @/tmp/dbus-DOriWtQmunix 3 [ ] STREAM CONNECTED 201617unix 3 [ ] STREAM CONNECTED 182920unix 3 [ ] STREAM CONNECTED 68899 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 70681 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 69664unix 3 [ ] STREAM CONNECTED 25426unix 3 [ ] STREAM CONNECTED 23136unix 3 [ ] STREAM CONNECTED 211410unix 3 [ ] STREAM CONNECTED 71507unix 2 [ ] DGRAM 71356unix 3 [ ] STREAM CONNECTED 71204 @/tmp/dbus-24cwLSLIEjunix 3 [ ] STREAM CONNECTED 23154 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 87226unix 3 [ ] STREAM CONNECTED 84364unix 3 [ ] STREAM CONNECTED 212422 @/dbus-vfs-daemon/socket-EfhZVgKJunix 3 [ ] STREAM CONNECTED 83559unix 3 [ ] SEQPACKET CONNECTED 68353unix 2 [ ] DGRAM 70312unix 3 [ ] STREAM CONNECTED 58586 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 46068 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 216416unix 3 [ ] SEQPACKET CONNECTED 182917unix 3 [ ] SEQPACKET CONNECTED 68387unix 3 [ ] STREAM CONNECTED 70060 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 69666unix 3 [ ] STREAM CONNECTED 59030unix 3 [ ] STREAM CONNECTED 58817 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 21436 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 215307 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 58854unix 3 [ ] STREAM CONNECTED 38455unix 3 [ ] STREAM CONNECTED 202971 /run/user/1000/vscode-10a394bb-1.27.1-shared.sockunix 3 [ ] STREAM CONNECTED 87228unix 3 [ ] STREAM CONNECTED 46006unix 3 [ ] STREAM CONNECTED 83557unix 3 [ ] STREAM CONNECTED 70333unix 3 [ ] STREAM CONNECTED 56147unix 3 [ ] STREAM CONNECTED 57531unix 3 [ ] STREAM CONNECTED 27680 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 182919unix 3 [ ] STREAM CONNECTED 71407 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 70672 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 62452 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 69665 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 62871unix 3 [ ] STREAM CONNECTED 47137unix 3 [ ] STREAM CONNECTED 23321unix 3 [ ] STREAM CONNECTED 199533unix 3 [ ] STREAM CONNECTED 70335 /run/user/1000/pulse/nativeunix 3 [ ] STREAM CONNECTED 63067unix 3 [ ] STREAM CONNECTED 59855 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 23155 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 88203 @/tmp/.X11-unix/X0unix 2 [ ] DGRAM 68746unix 3 [ ] STREAM CONNECTED 61904 @/tmp/dbus-DOriWtQmunix 3 [ ] STREAM CONNECTED 210670unix 3 [ ] STREAM CONNECTED 83566unix 3 [ ] STREAM CONNECTED 70339 @/tmp/.X11-unix/X0unix 3 [ ] STREAM CONNECTED 71119unix 3 [ ] STREAM CONNECTED 57561unix 2 [ ] DGRAM 23326unix 3 [ ] STREAM CONNECTED 26793unix 3 [ ] STREAM CONNECTED 24890unix 3 [ ] STREAM CONNECTED 182921unix 3 [ ] STREAM CONNECTED 83573unix 3 [ ] STREAM CONNECTED 68738unix 2 [ ] DGRAM 70686unix 3 [ ] STREAM CONNECTED 69684unix 3 [ ] STREAM CONNECTED 69651 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 33026 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 215306unix 3 [ ] STREAM CONNECTED 202732unix 3 [ ] STREAM CONNECTED 202561 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 71506unix 3 [ ] STREAM CONNECTED 71501 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 71207unix 3 [ ] STREAM CONNECTED 63064 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 58587unix 3 [ ] STREAM CONNECTED 57538unix 3 [ ] STREAM CONNECTED 47141unix 3 [ ] STREAM CONNECTED 217174unix 2 [ ] DGRAM 87216unix 3 [ ] STREAM CONNECTED 68263unix 3 [ ] STREAM CONNECTED 67673 /run/systemd/journal/stdoutunix 3 [ ] SEQPACKET CONNECTED 202545unix 3 [ ] STREAM CONNECTED 189839unix 3 [ ] SEQPACKET CONNECTED 68354unix 3 [ ] STREAM CONNECTED 70313unix 3 [ ] STREAM CONNECTED 23138 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 191826unix 3 [ ] STREAM CONNECTED 182922unix 3 [ ] STREAM CONNECTED 71503 @/tmp/dbus-DOriWtQmunix 3 [ ] STREAM CONNECTED 70688unix 3 [ ] STREAM CONNECTED 67951unix 3 [ ] STREAM CONNECTED 70679 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 60154 /var/run/docker/containerd/docker-containerd.sockunix 3 [ ] STREAM CONNECTED 23137 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 202733unix 3 [ ] STREAM CONNECTED 71442unix 3 [ ] STREAM CONNECTED 201698unix 3 [ ] STREAM CONNECTED 84646 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 67786unix 3 [ ] STREAM CONNECTED 63062unix 3 [ ] STREAM CONNECTED 55972unix 3 [ ] STREAM CONNECTED 213153 @/dbus-vfs-daemon/socket-sRZNEvTMunix 3 [ ] STREAM CONNECTED 82423unix 3 [ ] STREAM CONNECTED 68057 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 182910unix 3 [ ] STREAM CONNECTED 69012unix 3 [ ] STREAM CONNECTED 70302unix 3 [ ] STREAM CONNECTED 69678 @/tmp/dbus-24cwLSLIEjunix 3 [ ] STREAM CONNECTED 67928unix 3 [ ] STREAM CONNECTED 59037unix 2 [ ] DGRAM 27649unix 3 [ ] STREAM CONNECTED 85125unix 3 [ ] STREAM CONNECTED 71203unix 3 [ ] STREAM CONNECTED 58819 @/tmp/.X11-unix/X0unix 2 [ ] DGRAM 68260unix 3 [ ] STREAM CONNECTED 63078 /run/user/1000/busunix 3 [ ] SEQPACKET CONNECTED 83565unix 3 [ ] STREAM CONNECTED 69037unix 3 [ ] STREAM CONNECTED 57571 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 202675unix 3 [ ] STREAM CONNECTED 69707unix 3 [ ] STREAM CONNECTED 70676 @/tmp/dbus-24cwLSLIEjunix 3 [ ] STREAM CONNECTED 62453 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 27665unix 3 [ ] STREAM CONNECTED 68272 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 63063unix 3 [ ] STREAM CONNECTED 214561 @/dbus-vfs-daemon/socket-d3pL57RDunix 3 [ ] STREAM CONNECTED 87215unix 3 [ ] STREAM CONNECTED 61959unix 3 [ ] STREAM CONNECTED 210646 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 83558unix 3 [ ] STREAM CONNECTED 62519unix 3 [ ] STREAM CONNECTED 55110 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 57502unix 3 [ ] STREAM CONNECTED 216414unix 3 [ ] STREAM CONNECTED 182908unix 3 [ ] STREAM CONNECTED 83572unix 3 [ ] STREAM CONNECTED 70061 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 70677unix 3 [ ] STREAM CONNECTED 67930 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 62920unix 3 [ ] STREAM CONNECTED 60711 @/tmp/dbus-24cwLSLIEjunix 3 [ ] STREAM CONNECTED 47143unix 3 [ ] STREAM CONNECTED 47140unix 3 [ ] STREAM CONNECTED 236388unix 3 [ ] STREAM CONNECTED 202729unix 2 [ ] DGRAM 71443unix 3 [ ] STREAM CONNECTED 61239 @/tmp/.X11-unix/X0unix 3 [ ] STREAM CONNECTED 57539 @/tmp/.X11-unix/X0unix 2 [ ] DGRAM 26879unix 3 [ ] STREAM CONNECTED 201719unix 3 [ ] STREAM CONNECTED 68261unix 3 [ ] STREAM CONNECTED 67426unix 3 [ ] STREAM CONNECTED 210645unix 3 [ ] STREAM CONNECTED 210618 @/dbus-vfs-daemon/socket-ggG3Txrpunix 3 [ ] STREAM CONNECTED 83567unix 3 [ ] STREAM CONNECTED 68299 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 54592unix 3 [ ] STREAM CONNECTED 21472unix 3 [ ] STREAM CONNECTED 217159 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 191827 @/dbus-vfs-daemon/socket-9E4S5dArunix 3 [ ] STREAM CONNECTED 182909unix 3 [ ] STREAM CONNECTED 68737unix 3 [ ] STREAM CONNECTED 70678 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 69679unix 3 [ ] DGRAM 58128unix 3 [ ] STREAM CONNECTED 47142unix 3 [ ] STREAM CONNECTED 202730unix 3 [ ] STREAM CONNECTED 199538unix 3 [ ] STREAM CONNECTED 71502unix 3 [ ] STREAM CONNECTED 68271 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 57922unix 3 [ ] STREAM CONNECTED 201697unix 3 [ ] STREAM CONNECTED 184545unix 2 [ ] DGRAM 55887unix 3 [ ] STREAM CONNECTED 212420 /var/run/dbus/system_bus_socketunix 3 [ ] SEQPACKET CONNECTED 83564unix 3 [ ] STREAM CONNECTED 70323 @/tmp/dbus-24cwLSLIEjunix 3 [ ] STREAM CONNECTED 21471unix 3 [ ] STREAM CONNECTED 216418unix 3 [ ] STREAM CONNECTED 182911unix 3 [ ] SEQPACKET CONNECTED 68386unix 3 [ ] STREAM CONNECTED 70682 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 69677unix 2 [ ] DGRAM 62915unix 2 [ ] DGRAM 57432unix 3 [ ] STREAM CONNECTED 47136unix 3 [ ] STREAM CONNECTED 202549 @/tmp/.X11-unix/X0unix 3 [ ] STREAM CONNECTED 83569unix 3 [ ] STREAM CONNECTED 71382unix 3 [ ] STREAM CONNECTED 212390unix 3 [ ] STREAM CONNECTED 68262 @/tmp/dbus-DOriWtQmunix 3 [ ] STREAM CONNECTED 70192unix 3 [ ] STREAM CONNECTED 56151unix 3 [ ] STREAM CONNECTED 210655unix 3 [ ] STREAM CONNECTED 202685unix 3 [ ] STREAM CONNECTED 83555unix 3 [ ] STREAM CONNECTED 70322unix 3 [ ] STREAM CONNECTED 202676unix 3 [ ] STREAM CONNECTED 68699unix 3 [ ] STREAM CONNECTED 70675unix 3 [ ] STREAM CONNECTED 69671 @/tmp/.X11-unix/X0unix 3 [ ] STREAM CONNECTED 67764unix 3 [ ] STREAM CONNECTED 62872unix 3 [ ] STREAM CONNECTED 25400 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 201636 /run/user/1000/pulse/nativeunix 3 [ ] STREAM CONNECTED 71450unix 3 [ ] STREAM CONNECTED 58074unix 3 [ ] STREAM CONNECTED 59704 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 57266 @/tmp/dbus-24cwLSLIEjunix 3 [ ] STREAM CONNECTED 27687 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 201720unix 3 [ ] STREAM CONNECTED 185544 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 67429unix 2 [ ] DGRAM 242115unix 3 [ ] STREAM CONNECTED 190330 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 80602unix 3 [ ] STREAM CONNECTED 61894unix 3 [ ] STREAM CONNECTED 16371 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 202858unix 3 [ ] STREAM CONNECTED 184351unix 3 [ ] STREAM CONNECTED 62445unix 3 [ ] STREAM CONNECTED 58827 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 62197unix 3 [ ] STREAM CONNECTED 80879unix 3 [ ] STREAM CONNECTED 68879unix 3 [ ] STREAM CONNECTED 63222 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 201652unix 3 [ ] STREAM CONNECTED 80601unix 3 [ ] STREAM CONNECTED 78311unix 3 [ ] STREAM CONNECTED 71553 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 202859unix 3 [ ] STREAM CONNECTED 62446 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 60606 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 68337 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 67929 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 67740 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 80880unix 3 [ ] STREAM CONNECTED 69020 @/tmp/dbus-24cwLSLIEjunix 3 [ ] STREAM CONNECTED 67905unix 2 [ ] DGRAM 27677unix 3 [ ] SEQPACKET CONNECTED 80594unix 3 [ ] STREAM CONNECTED 61902unix 3 [ ] STREAM CONNECTED 57957 @/tmp/dbus-24cwLSLIEjunix 3 [ ] STREAM CONNECTED 45319unix 3 [ ] DGRAM 21311unix 3 [ ] STREAM CONNECTED 3698unix 2 [ ] DGRAM 78966unix 3 [ ] STREAM CONNECTED 62420unix 3 [ ] STREAM CONNECTED 59992unix 3 [ ] STREAM CONNECTED 26142unix 3 [ ] STREAM CONNECTED 71458 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 70669unix 3 [ ] STREAM CONNECTED 67624 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 80539 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 71556 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 70228 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 62247unix 3 [ ] STREAM CONNECTED 23151 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 185546unix 3 [ ] STREAM CONNECTED 70196unix 3 [ ] STREAM CONNECTED 61903 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 16368 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 200686unix 3 [ ] STREAM CONNECTED 188954unix 3 [ ] STREAM CONNECTED 78978unix 3 [ ] STREAM CONNECTED 62421 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 61595unix 3 [ ] STREAM CONNECTED 35740unix 3 [ ] STREAM CONNECTED 68334 @/tmp/.ICE-unix/2219unix 3 [ ] STREAM CONNECTED 62218unix 3 [ ] SEQPACKET CONNECTED 80595unix 3 [ ] STREAM CONNECTED 71552unix 3 [ ] STREAM CONNECTED 70425unix 3 [ ] STREAM CONNECTED 71221 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 61216 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 56269 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 199532 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 62455unix 3 [ ] DGRAM 58129unix 3 [ ] STREAM CONNECTED 40672 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 80650unix 3 [ ] STREAM CONNECTED 71457unix 3 [ ] STREAM CONNECTED 67572 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 81453unix 3 [ ] STREAM CONNECTED 77714 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 70448 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 201651unix 3 [ ] STREAM CONNECTED 189026 @/tmp/dbus-DOriWtQmunix 3 [ ] STREAM CONNECTED 70427unix 3 [ ] STREAM CONNECTED 61905unix 3 [ ] STREAM CONNECTED 58850unix 3 [ ] STREAM CONNECTED 202555 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 62418unix 3 [ ] STREAM CONNECTED 59847unix 2 [ ] DGRAM 35040unix 3 [ ] STREAM CONNECTED 190647unix 3 [ ] STREAM CONNECTED 63136unix 2 [ ] DGRAM 62136unix 3 [ ] STREAM CONNECTED 80537 @/tmp/.X11-unix/X0unix 3 [ ] STREAM CONNECTED 69019unix 3 [ ] STREAM CONNECTED 68823unix 2 [ ] DGRAM 68743unix 3 [ ] STREAM CONNECTED 67904 @/tmp/dbus-24cwLSLIEjunix 3 [ ] STREAM CONNECTED 67425 @/tmp/dbus-DOriWtQmunix 3 [ ] STREAM CONNECTED 64303 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 183245 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 71435unix 3 [ ] STREAM CONNECTED 62423unix 3 [ ] STREAM CONNECTED 59997 @/tmp/.X11-unix/X0unix 3 [ ] STREAM CONNECTED 23148 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 189829 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 71451unix 3 [ ] STREAM CONNECTED 63125unix 3 [ ] STREAM CONNECTED 200685unix 3 [ ] STREAM CONNECTED 68844unix 3 [ ] STREAM CONNECTED 70199 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 62248 /run/user/1000/busunix 3 [ ] SEQPACKET CONNECTED 80597unix 3 [ ] STREAM CONNECTED 58848 @/tmp/.X11-unix/X0unix 2 [ ] DGRAM 23807unix 3 [ ] STREAM CONNECTED 200697unix 3 [ ] STREAM CONNECTED 62424 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 202970unix 3 [ ] STREAM CONNECTED 62155 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 62146unix 3 [ ] DGRAM 2815unix 3 [ ] STREAM CONNECTED 80883unix 3 [ ] STREAM CONNECTED 68880 @/tmp/.X11-unix/X0unix 3 [ ] STREAM CONNECTED 62198unix 3 [ ] STREAM CONNECTED 54535unix 3 [ ] STREAM CONNECTED 77732 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 45320unix 3 [ ] STREAM CONNECTED 202554 @/tmp/.X11-unix/X0unix 3 [ ] STREAM CONNECTED 68209unix 3 [ ] STREAM CONNECTED 69984 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 62394unix 3 [ ] STREAM CONNECTED 58014unix 3 [ ] STREAM CONNECTED 67739unix 3 [ ] STREAM CONNECTED 62122unix 3 [ ] STREAM CONNECTED 55622 /var/run/dbus/system_bus_socketunix 2 [ ] DGRAM 2809unix 3 [ ] STREAM CONNECTED 69021unix 3 [ ] STREAM CONNECTED 61857unix 2 [ ] DGRAM 23329unix 2 [ ] DGRAM 202853unix 3 [ ] STREAM CONNECTED 186543unix 3 [ ] STREAM CONNECTED 70363 @/tmp/dbus-24cwLSLIEjunix 3 [ ] STREAM CONNECTED 62397 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 27678unix 3 [ ] STREAM CONNECTED 74322 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 70671unix 3 [ ] STREAM CONNECTED 67674 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 56681unix 3 [ ] DGRAM 2816unix 3 [ ] STREAM CONNECTED 81454unix 3 [ ] STREAM CONNECTED 70164 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 63184 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 27689 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 233069 /run/user/1000/pulse/nativeunix 2 [ ] DGRAM 201655unix 3 [ ] STREAM CONNECTED 190327unix 3 [ ] STREAM CONNECTED 61897unix 3 [ ] STREAM CONNECTED 22750unix 3 [ ] STREAM CONNECTED 188955 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 183244 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 68893 @/tmp/dbus-24cwLSLIEjunix 3 [ ] STREAM CONNECTED 62447unix 3 [ ] STREAM CONNECTED 60078 @/tmp/.X11-unix/X0unix 3 [ ] STREAM CONNECTED 67611 /run/systemd/journal/stdoutunix 2 [ ] DGRAM 81455unix 3 [ ] STREAM CONNECTED 62214unix 3 [ ] STREAM CONNECTED 22979 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 68357 @/tmp/.X11-unix/X0unix 3 [ ] STREAM CONNECTED 61901unix 3 [ ] STREAM CONNECTED 58611unix 3 [ ] STREAM CONNECTED 200690unix 3 [ ] STREAM CONNECTED 188956unix 3 [ ] STREAM CONNECTED 62419 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 62923unix 3 [ ] STREAM CONNECTED 27673unix 3 [ ] STREAM CONNECTED 63134unix 2 [ ] DGRAM 62129unix 2 [ ] DGRAM 62929unix 3 [ ] STREAM CONNECTED 202552 @/tmp/dbus-24cwLSLIEjunix 3 [ ] STREAM CONNECTED 71273 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 67614 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 26984 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 190328 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 78979 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 63068 @/tmp/dbus-DOriWtQmunix 3 [ ] STREAM CONNECTED 27772unix 3 [ ] STREAM CONNECTED 184350unix 3 [ ] STREAM CONNECTED 68892unix 3 [ ] STREAM CONNECTED 62395 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 80649unix 3 [ ] STREAM CONNECTED 23057unix 3 [ ] STREAM CONNECTED 80882unix 3 [ ] STREAM CONNECTED 70447unix 3 [ ] STREAM CONNECTED 67903unix 3 [ ] STREAM CONNECTED 190329unix 3 [ ] STREAM CONNECTED 68259 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 63039 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 58851unix 3 [ ] STREAM CONNECTED 202866unix 3 [ ] STREAM CONNECTED 71275 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 69673 @/tmp/.X11-unix/X0unix 3 [ ] STREAM CONNECTED 57945unix 3 [ ] STREAM CONNECTED 71459unix 3 [ ] STREAM CONNECTED 63419unix 3 [ ] STREAM CONNECTED 67547 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 30658 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 80881unix 2 [ ] DGRAM 71208unix 3 [ ] STREAM CONNECTED 70120 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 67635 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 231109unix 3 [ ] STREAM CONNECTED 191829unix 3 [ ] STREAM CONNECTED 186556 /var/run/dbus/system_bus_socketunix 3 [ ] SEQPACKET CONNECTED 80598unix 3 [ ] STREAM CONNECTED 71460 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 61238 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 58847unix 3 [ ] STREAM CONNECTED 26899 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 3769unix 3 [ ] STREAM CONNECTED 186544unix 3 [ ] STREAM CONNECTED 78335 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 68211unix 3 [ ] STREAM CONNECTED 71274 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 62396unix 3 [ ] STREAM CONNECTED 62525 @/containerd-shim/moby/2b6de2c6dd04f14842848f72d2d353c053adcab4d8351ff3cf91bfa0575377fe/shim.sock@unix 3 [ ] STREAM CONNECTED 27679unix 3 [ ] STREAM CONNECTED 70670 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 67688 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 28413 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 68338unix 3 [ ] STREAM CONNECTED 60048 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 24538 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 188957 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 70202 /run/user/1000/busunix 3 [ ] STREAM CONNECTED 68210unix 3 [ ] STREAM CONNECTED 62448 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 78072unix 3 [ ] STREAM CONNECTED 70193 /run/systemd/journal/stdoutunix 3 [ ] STREAM CONNECTED 62147 /var/run/dbus/system_bus_socketunix 3 [ ] STREAM CONNECTED 68985unix 3 [ ] STREAM CONNECTED 62213AslanFrench (talk) 06:07, 19 October 2018 (UTC)- I think I may have figured out the issue. When I run `curl https://wiki.example.com/api.php` I get the mediawiki api page, but when I run the same thing but with http, I get an error code.
- I also notice that my LocalSettings.php file says https://wiki.example.com/w/api.php Which is says that because that's what the set up guide says to do (though I also see recommendations against it on other pages. It's very unclear what is the right way to do things).
- If I go to wiki.example.com/w/api.php I get a "file does not exist response" but if I go to wiki.example.com/api.php then I get a correct response.
- I changed my settings in LocalSettings.php and restarted nginx and parsoid but VE still doesn't work. I'm going to try restarting my computer again and see if that helps. AslanFrench (talk) 06:33, 19 October 2018 (UTC)
- Hmmm.... interesting.
- Okay so I made sure to delete all the files that I had created when I tried that first tutorial. I restarted the computer. I run curl localhost:8142
- Again, no response. I run curl localhost:8000
- No response! But it was just working! So I realized.... oh, the Parsoid Setup never had a place to tell me to actually start the parsoid node server. So I go to the only remaining parsoid installation /usr/lib/parsoid/bin/server.js and I run node server.js
- I run curl localhost:8000 and it's a success!!! I restart nginx and parsoid and then open up VE and.... still doesn't work. I can get https://wiki.example.com/api.php no problem. I can get localhost:8000 no problem. And I have everything set in the localsettings.php file the exact same as it should be configured with parsoid.... but.. no love? Both parts of up but not connecting. AslanFrench (talk) 06:48, 19 October 2018 (UTC)
/usr/lib/parsoid/none_modoles/lib/ folder not being created
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hello,
I followed the instructions from here to configure repository and install parsoid, and I see a few odd things, 1, /var/log/parsoid is owned by the parsoid user and group, and I have to change it to parsoid:adm and give the adm group read permissions to see the parsoid.log file, and 2, when i try to start the parsoid log service I get the message:
{"name":"parsoid","hostname":"wiki","pid":1220,"level":30,"levelPath":"info/service-runner","msg":"master(1220) initializing 1 workers","time":"2018-10-19T20:04:52.048Z","v":0}
{"name":"parsoid","hostname":"wiki","pid":1231,"level":60,"err":{"message":"Cannot find module '/usr/lib/parsoid/node_modules/lib/index.js'","name":"Error","stack":"Error: Cannot find module '/usr/lib/parsoid/node_modules/lib/index.js'\n at Function.Module._resolveFilename (module.js:547:15)\n at Function.Module._load (module.js:474:25)\n at Module.require (module.js:596:17)\n at require (internal/module.js:11:18)\n at Worker._requireModule (/usr/lib/parsoid/node_modules/service-runner/lib/base_service.js:342:30)\n at Worker._requireModule (/usr/lib/parsoid/node_modules/service-runner/lib/base_service.js:362:29)\n at Worker._requireModule (/usr/lib/parsoid/node_modules/service-runner/lib/base_service.js:362:29)\n at P.map (/usr/lib/parsoid/node_modules/service-runner/lib/worker.js:168:25)\n at tryCatcher (/usr/lib/parsoid/node_modules/bluebird/js/release/util.js:16:23)\n at MappingPromiseArray._promiseFulfilled (/usr/lib/parsoid/node_modules/bluebird/js/release/map.js:61:38)\n at MappingPromiseArray.PromiseArray._iterate (/usr/lib/parsoid/node_modules/bluebird/js/release/promise_array.js:114:31)\n at MappingPromiseArray.init (/usr/lib/parsoid/node_modules/bluebird/js/release/promise_array.js:78:10)\n at MappingPromiseArray._asyncInit (/usr/lib/parsoid/node_modules/bluebird/js/release/map.js:30:10)\n at Async._drainQueue (/usr/lib/parsoid/node_modules/bluebird/js/release/async.js:138:12)\n at Async._drainQueues (/usr/lib/parsoid/node_modules/bluebird/js/release/async.js:143:10)\n at Immediate.Async.drainQueues (/usr/lib/parsoid/node_modules/bluebird/js/release/async.js:17:14)","code":"MODULE_NOT_FOUND","moduleName":"lib/index.js","levelPath":"fatal/service-runner/worker"},"msg":"Cannot find module '/usr/lib/parsoid/node_modules/lib/index.js'","time":"2018-10-19T20:04:52.838Z","v":0}
{"name":"parsoid","hostname":"wiki","pid":1220,"level":40,"message":"first worker died during startup, continue startup","worker_pid":1231,"exit_code":1,"startup_attempt":1,"levelPath":"warn/service-runner/master","msg":"first worker died during startup, continue startup","time":"2018-10-19T20:04:53.849Z","v":0}
The /usr/lib/parsoid/none_modules/lib folder does not seem to exist
Running ubuntu Ubuntu 18.04.1 LTS
Thank you, Vaerchi (talk) 20:45, 19 October 2018 (UTC)
- How did you install Parsoid? With apt-get? Arlolra (talk) 18:20, 22 October 2018 (UTC)
- Yes,
- 854 apt-get install software-properties-common
- 855 root apt-get install software-properties-common
- 856 sudo apt-get install software-properties-common
- 857 sudo apt install dirmngr
- 858 sudo apt-key advanced --keyserver keys.gnupg.net --recv-keys 90E9F83F22250DD7
- 859 sudo apt install apt-transport-https
- 860 sudo apt update && sudo apt install parsoid 66.103.132.84 (talk) 17:18, 24 October 2018 (UTC)
- And what command are you issuing to start the service? Arlolra (talk) 17:34, 6 November 2018 (UTC)
Cannot GET /localhost/mywiki/v3/transform/wikitext/to/html
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hello,
I've been having trouble issuing the wikitext to html command for a whole MediaWiki page. I've tried out the parse.js program on small text, but I need to be able to convert wikitext to html for a whole page. In the long-run, I'll need to be able to do it for several pages.
I tried recreating the command listed in mediawiki.org/wiki/Parsoid/API#For_wikitext_->_HTML_requests:
/:domain/v3/page/:format/:title/:revision?
by using :
http://localhost:8000/localhost/mywiki/v3/transform/wikitext/to/html
where 'localhost/mywiki' is the path to my wiki's main page (I have another page, titled 'Sandbox', located at localhost/mywiki/index.php/Sandbox that I'd like to run wikitext to html on).
However, the above command I tried out returned the following:
Cannot GET /localhost/mywiki/v3/transform/wikitext/to/html
What is the proper implementation of this command? Or should I be doing something different? Emske (talk) 19:10, 2 November 2018 (UTC)
- The domain part of /:domain/v3/page/:format/:title/:revision? is supposed to correspond to what you've defined in your config.yaml
- I imagine you've got something like,
- mwApis:
- - uri: 'http://localhost/mywiki/api.php'
domain: 'localhost'- In which case, you'd want to query,
- http://localhost:8000/localhost/v3/page/html/Main_Page
- or
- http://localhost:8000/localhost/v3/page/html/Sandbox
- Note that urls with "transform" in the path only accept POST requests.
- See https://github.com/wikimedia/parsoid/blob/master/lib/api/ParsoidService.js#L212-L214 Arlolra (talk) 20:11, 2 November 2018 (UTC)
- Hi Arlolra,
- Thank you so much for the swift response. The latter query appears to have worked. It displayed my Sandbox page in HTML.
- However, I would like the HTML code dump (preferably in a txt file, but I think JSON would also work). Is there a way to output the actual HTML?
- Thanks so much again! Emske (talk) 18:28, 5 November 2018 (UTC)
- Try,
node bin/parse.js --config --domain localhost --pageName Sandbox < /dev/nullArlolra (talk) 17:30, 6 November 2018 (UTC)- I tried that; the system couldn't find the path specified (I'm guessing /dev/null, but I can look through the parsoid or node_modules directory to try a different path).
- I tried executing without < /dev/null and got:
- Waiting for stdin...
- What input is it waiting on? I thought the Sandbox for the --page flag wouldn't covered that? Emske (talk) 19:36, 6 November 2018 (UTC)
- If you supply an input with the --pageName argument set, it parses the input in the context of the page. If no input is supplied, it'll fetch the source for that page. If you hit ctrl-c when it says "Waiting for stdin ..." it should do what you expect. Piping in < /dev/null is another way of achieving the same thing. Arlolra (talk) 15:45, 13 November 2018 (UTC)
Code block not visible with VisualEditor when using https
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hi
I followed the hints found in "Extension:VisualEditor#Parsoid over HTTPS". It works pretty well. The only problem I'm confronted with is that after inserting a code block element only "<>" is shown when done. If I save the document and reopen it for editing nothing of the code blocks can be seen. I need to use the source code editor then.
Does anybody hav a hint whats wrong here and how to solve the issue?
Regards
Bernd SpaetzleBinLinsen (talk) 08:51, 12 November 2018 (UTC)
- I don't really know. But, there was another recent thread that had some odd behaviors, which were resolved by turning on "selective serialization" with RESTbase. Does that sound like it might be relevant? Whatamidoing (WMF) (talk) 23:23, 12 November 2018 (UTC)
- This sounds more as there is a problem, that some spaces are deleted.
- I do not loose the code blocks they are just not shown when opening the wiki page with the VisualEditor. If I use source code editing anything is as it should be.
- But I would give it a try. Can somebody explain how the "selective serialization" is turned on?
- BTW. My Setup ist mediawiki 1.31-alpha, parsoid 0.9 SpaetzleBinLinsen (talk) 07:19, 13 November 2018 (UTC)
- This is the visual editor, so obviously, you won't see markup but the rendering of markup. If you want to see and edit markup, you have to use source code editing. So, can you be a bit more specific about the problem with "code blocks"?
- 1. What is the code block you insert in VE?
- 2. What is the code that you see in wikitext editor? SSastry (WMF) (talk) 15:36, 13 November 2018 (UTC)
- This doesn't sound a like an issue that requires selective serialization to resolve. That only comes into play when saving a page.
- Can you clarify what you mean by a code block element? Arlolra (talk) 15:37, 13 November 2018 (UTC)
Error while installing Parsoid
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
npm WARN deprecated circular-json@0.3.1: CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated formidable@1.0.17: Old versions of Formidable are not compatible with the current Node.js; Upgrade to 1.2.0 or later
npm WARN deprecated is-my-json-valid@2.16.0: catastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 2.17.2 as soon as possible
npm WARN deprecated jade@0.26.3: Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated kad-fs@0.0.4: Please upgrade to @kadenceproject/kadence - See https://kadence.github.io
npm WARN deprecated kad-memstore@0.0.1: Please upgrade to @kadenceproject/kadence - See https://kadence.github.io
npm WARN deprecated minimatch@0.3.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated nsp@2.8.1: The Node Security Platform service is shutting down 9/30 - https://blog.npmjs.org/post/175511531085/the-node-security-platform-service-is-shutting
npm WARN deprecated joi@6.10.1: This version is no longer maintained. Please upgrade to the latest version.
npm WARN deprecated wreck@6.3.0: This version is no longer maintained. Please upgrade to the latest version.
npm WARN deprecated to-iso-string@0.0.2: to-iso-string has been deprecated, use @segment/to-iso-string instead.
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN system32 No description
npm WARN system32 No repository field.
npm WARN system32 No license field. Adithyak1997 (talk) 10:22, 13 November 2018 (UTC)
- Those look like warnings, not errors. In any case, Parsoid development to this point has been with npm v3 (or, possibly v4). See Parsoid/Upgrade packages Arlolra (talk) 15:32, 13 November 2018 (UTC)
- Is this Parsoid currently working?I actually wanted to run Linter gadget. Adithyak1997 (talk) 15:36, 13 November 2018 (UTC)
- I'm going to assume you mean the Linter extension, which requires Parsoid. It sounds like you may have installed it correctly, but you'll need to verify that it's configured and running. Arlolra (talk) 15:39, 13 November 2018 (UTC)
- @Arlolra, I have a doubt. In the page Parsoid/Upgrade packages, my laptop cmd does not support the last code fragment. How can I then execute it in cmd? Also, is it mandatory that media wiki extension needs to be downloaded inorder to install Parsoid? Adithyak1997 (talk) 18:00, 13 November 2018 (UTC)
- You can lint a page without the MediaWiki Linter extension installed but the results would be loggged to the command line. The two are meant to work in concert so that the results of linting are posted to MediaWiki for storage and displaying. Arlolra (talk) 19:31, 17 July 2019 (UTC)
Installing Parsoid using the node.js App Manager cPanel provides
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Some web hosting providers (like Namecheap) have enabled the "Setup Node.js App" option in the options list, which is a weird version of Node that I assume is sandboxed
I ran the NPM Install, however I am getting an Permission Denied when trying to execute npm start
(ssh of course) GlitchyPSI (talk) 22:02, 16 November 2018 (UTC)
- Can you provide a paste of the error? Unfortunately we probably can't provide much help with that environment. Arlolra (talk) 19:28, 17 July 2019 (UTC)
Check which version of parsoid is installed
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
I think I saw this somewhere but I cannot remember where and cannot find it right now. How do I check for the version of parsoid I am currently running? [[kgh]] (talk) 16:57, 17 November 2018 (UTC)
- Ok. Go to `/usr/lib/parsoid/src`, open "package.json" and look for the version stated. However I have the strong feeling that there is a saner method around. [[kgh]] (talk) 17:05, 17 November 2018 (UTC)
$ curl "http://localhost:8141/version"{"name":"parsoid","version":"0.9.0"}- (Or whatever port/IP you have parsoid running on :-)) Legoktm (talk) 04:52, 18 November 2018 (UTC)
- One other method that worked for me (on Ubuntu):
dpkg -s parsoid
- Or, maybe more specifically:
dpkg -s parsoid | grep VersionBryandamon (talk) 21:32, 5 February 2020 (UTC)
- That will work for anyone who installed via the Debian/Ubuntu package only (but is still convenient nonetheless). Legoktm (talk) 07:30, 7 February 2020 (UTC)
Transclusion of tags is not being done correctly
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hi,
I am trying to use citation tool and Citoid with the VisualEditor to allow easy management of references on my MediaWiki instance.
When I insert a link, Citoid service retrieves correctly the content of the source and build a reference accordingly. However, the following is being added at the end of the reference:
"<templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>"
It seems that Parsoid is directly responsible of this bug. Indeed, when I add a reference inside VisualEditor, a POST to the API is being made, which gives the following response:
As you can see, the content is not parsing the templatestyles tags as it should, thus, those are displayed in VisualEditor.
I don't know if the following issues are related, and if so, to what extent:
https://phabricator.wikimedia.org/T88019
https://phabricator.wikimedia.org/T188143
Notice that when I save the edit, the tags are dropped but the reference is still here, as it should.
Does someone know what is causing this issue, and how can I resolve it? Thank you in advance. Hwgen22 (talk) 11:50, 29 November 2018 (UTC)
- Is your wiki public? What versions of Parsoid, MW, and VE do you run? SSastry (WMF) (talk) 14:59, 29 November 2018 (UTC)
- Do you have this extension installed?
- https://www.mediawiki.org/wiki/Extension:TemplateStyles Arlolra (talk) 15:34, 29 November 2018 (UTC)
- Without the TemplateStyles extension, Parsoid won't recognize those tags so they won't be rendered as scripts and just output as literal text as you're seeing. Arlolra (talk) 15:35, 29 November 2018 (UTC)
- Hi @SSastry (WMF), hi @Arlolra,
- Thank you for your responses.
- Unfortunately, my wiki is hosted locally, on a virtual machine, as I am doing some configuration for now, prior to making it public.
- I use MediaWiki 1.31.1, Parsoid 0.9.0 and VisualEditor 0.1.0 (6854ea0).
- I already have TemplateStyles extension installed. At least, it shows in Special:Version (version 1.0 (e5da5c0)).
- In Parser extension tags, I have the following: "<gallery>, <indicator>, <nowiki>, <syntaxhighlight lang='text'>, <ref>, <references>, <templatedata> and <templatestyles>".
Can the order of invocation of extensions in LocalSettings.php be a problem? For your information, this is the order that I have: Cite, ParserFunctions (with and without $wgPFEnableStringFunctions enabled, currently it is disabled), WikiEditor, VisualEditor, <VisualEditor configuration>, <parsoid configuration>, Scribunto, TemplateData, TemplateStyles, <TemplateStyles configutation>, Citoid, <Citoid configuration>. If the order is not a problem, do you know what could cause such issue? Thank you very much for your help. Hwgen22 (talk) 10:00, 30 November 2018 (UTC)
- Hopefully this problem was resolved since the paste above has expired. Arlolra (talk) 19:26, 17 July 2019 (UTC)
upgrade from 9 to 10 resulted in curl error: 7
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hello, after the upgrade clicking on edit displayed:
Error loading data from server: apierror-visualeditor-docserver-http-error: (curl error: 7) Couldn't connect to server. Would you like to retry?
/var/log/parsoid/parsoid.log ;
{"name":"parsoid","hostname":"wiki","pid":4318,"level":30,"levelPath":"info/service-runner","msg":"master(4318) initializing 2 workers","time":"2018-12-08T16:22:00.405Z","v":0}
{"name":"parsoid","hostname":"wiki","pid":4328,"level":60,"levelPath":"fatal/service-runner/worker","msg":"Cannot set property 'worker_id' of null","time":"2018-12-08T16:22:01.185Z","v":0}
{"name":"parsoid","hostname":"wiki","pid":4318,"level":40,"message":"first worker died during startup, continue startup","worker_pid":4328,"exit_code":1,"startup_attempt":1,"levelPath":"warn/service-runner/master","msg":"first worker died during startup, continue startup","time":"2018-12-08T16:22:02.196Z","v":0}
we are using Debian Stretch
MediaWiki 1.31.1 (a4c8065) 13:59, September 20, 2018
nodejs Version: 4.8.2~dfsg-1
curl Version: 7.52.1-5+deb9u8
parsoid settings:
# cat /etc/mediawiki/parsoid/settings.js
'use strict';
exports.setup = function(parsoidConfig) {
parsoidConfig.setMwApi({ uri: 'http://localhost/mediawiki/api.php' , prefix: 'localhost', domain: 'localhost' });
parsoidConfig.useSelser = true;
};
Any suggestions to try to fix this appreciated! RobFantini (talk) 13:36, 9 December 2018 (UTC)
- 0.9.0 was the last version to support node v4.x
- See the release notes https://www.mediawiki.org/wiki/Parsoid/Releases#0.9.0_(released_Mar_23,_2018)
- You'll need to upgrade node to v6.x Arlolra (talk) 17:40, 9 December 2018 (UTC)
- thank you, so this fixed it
apt-get -t stretch-backports install nodejsRobFantini (talk) 20:36, 9 December 2018 (UTC)- Hello,
- updating node.js to 8.11.1 will restore functionality of creating new pages, however editing of existing does not work: "apierror-visualeditor-docserver-http: HTTP 406"
- any support in this matter will be appreciated. 109.199.10.165 (talk) 20:51, 10 December 2018 (UTC)
- Which version of Parsoid are you coming from? Arlolra (talk) 16:28, 11 December 2018 (UTC)
- I also get HTTP 406 when I edit existing pages using the latest Parsoid version (10.0.0) Magol (talk) 14:45, 18 December 2018 (UTC)
- This is the result of content version mismatches between Parsoid and VE
- See https://www.mediawiki.org/wiki/Parsoid/Releases and https://lists.wikimedia.org/pipermail/wikitech-l/2018-November/091121.html
- There's also somewhat maintained compatibility matrix at https://www.mediawiki.org/wiki/Extension:VisualEditor#Setting_up_VisualEditor Arlolra (talk) 19:05, 17 July 2019 (UTC)
Parsoid Troubleshooting guide
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Could someone update the troubleshooting guide? It seems to only be a "verify your Parsoid is working" instruction set with a lot of hidden internal comments, not a "troubleshooting guide." Also, should this this edit have been undone: https://www.mediawiki.org/w/index.php?title=Parsoid%2FTroubleshooting&type=revision&diff=3008571&oldid=3008537 ? My Parsoid doesn't seem to be working yet, so I can't tell if it was a good edit or not. TheMystics (talk) 20:53, 14 December 2018 (UTC)
- Alas, Parsoid is being ported to PHP to be included in core, which should obviate most of the pain here. Arlolra (talk) 19:09, 17 July 2019 (UTC)
Multiple wikis sharing the same parsoid service
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hi
i can't share multiple wikis on the same parsoid service.
"config.yaml" looks like that:
mwApis:
- # First wiki
uri: 'http://wiki1.mysite.com/api.php'
domain: 'wiki1.mysite.com' # optional
- # If you have another wiki on a different domain
uri: 'http://wiki2.mysite.com/api.php'
domain: 'wiki2.mysite.com' # optional
"Wiki1" is fully functionally
but in "wiki2" i can't edit a page. there is an error:
"apierror-visualeditor-docserver-http: HTTP 401"
i can do a change in "LocalSettings_wiki2.php" of Parsoid "Domain" to "wiki1.mysite.com". And now i can edit a page, but there is showing an other page of wiki1.
i have a LocalSettings.php who switch pages:
switch ( $_SERVER['SERVER_NAME'] ) {
case 'wiki1.mysite.com':
require_once 'LocalSettings_wiki1.php';
break;
case 'wiki2.mysite.com':
require_once 'LocalSettings_wiki2.php';
break;
and my "LocalSettings_wiki2.php" is showing:
#Link with Parsoid
$wgVirtualRestConfig['modules']['parsoid'] = array(
// URL to the Parsoid instance
'url' => 'http://wiki2.mysite.com:8000',
// Parsoid "domain", see below (optional)
'domain' => 'wiki2.mysite.com',
LocalSettings_wiki1.php is almost similar, only "url" and "Domain" are different but also port 8000
can someone help?
thanks a lot! LP371906 (talk) 14:17, 28 December 2018 (UTC)
- When I got this working, Parsoid had set its main service up on the top-level domain (localhost:8000 or mysite.com:8000). I believe the 'url' parameter in LocalSettings wants this value or where ever the shared instance of parsoid is running. Not the domain for your individual wikis.
- First, with parsoid running, check to see if it's running on the TLD.
- Either type 'curl http://mysite.com:8000' at a commandline or use a web browser to visit 'http://mysite.com:8000'. If that's where parsoid is running, you'll get back HTML code from the curl command or a 'Welcome to Parsoid' page.
- If that works, change the 'url' in $wgVirtualRestConfig to just 'http://mysite.com:8000' in your LocalSettings_wiki1.php and _wiki2.php. (But leave your config.yaml as is.) See if that fixes the errors.
PenDragyn21 (talk) 05:47, 10 January 2019 (UTC)- Hi PenDragyn21
- i've change my LocalSettings Config to:
- #Link with Parsoid
- $wgVirtualRestConfig['modules']['parsoid'] = array(
- // URL to the Parsoid instance
- 'url' => 'http://localhost:8000',
- // Parsoid "domain", see below (optional)
- 'domain' => 'wiki2.mysite.com',
- // Parsoid "prefix", see below (optional)
- 'prefix' => 'wiki2.mysite.com'
- );
- $wgVirtualRestConfig['modules']['parsoid']['forwardCookies'] = true;
- but i think the Problem was "forwardCookies" = true.
- many thanks! LP371906 (talk) 16:03, 17 January 2019 (UTC)