[03:06:48] When I install mediawiki with PostgreSQL, what is the database name and database usernames supposed to be? [03:08:18] it is supposed to be "postgres"? [03:23:10] https://dpaste.org/QsHm seriously, what am i doing wrong here? [03:36:04] Wait, so...it will fail if I try it with the same databasename and username the *first* time, but not hte second time? seriously confused [03:36:30] the issue was that i was deleting the database between each attempt. this has to be a bug [04:06:02] database name: the name you want your mediawiki database to be. "postgres" is 100% the wrong answer here [04:06:19] database username: a user you created in postgres with permission to create new tables in the chosen database [04:06:37] (generally you should create both the database and the user before running the mediawiki installer) [04:07:09] Skizzerz: I didn't put "postgres" as the database name [04:07:41] I tried probably 30+ times all different things, including creating the user and database separately, and just letting mediawiki do its own thing [04:08:11] and the only reason i got through was because...I think I just tried the defaults twice in a row [04:08:16] without deleting the database inbetween. [04:08:24] Really, I can't see how that's *not* a bug. [04:08:28] the most successful strategy would be to create both first, and ensure the user has proper permissions on the db, and then plug those values in [04:08:46] Well I didn't change *anything* about the permissions, and it still went through [04:09:05] this was happening before, but it just worked one time and I didn't figure out why. [04:09:26] When I tried to recreate the wiki from scratch again I got stuck on it for over an hour, and as far as I can tell, that's how I fixed it [04:09:40] if the user doesn't have permissions or the db doesn't exist, and you provide root credentials to the db server, mediawiki will attempt to create things for you or assign appropriate permissions [04:09:50] it does not always succeed in that endeavor [04:10:26] anyway, what version of mw are you installing, and what version of postgres are you using? [04:10:49] Right, but I tried the exact same thing literally *dozens* of times and it just arbitrarily works sometimes [04:11:51] But now I have the same issue I had before (which I havent' brought up here yet, because the entire point of me deleting everything and starting ove again was to fix this) [04:12:05] anyway, what version of mw are you installing, and what version of postgres are you using? [04:12:42] as I'm uploading an entire wiki to the database using importDump.php, when I click on random pages (all random pages) I get errors like this: The revision #1732 of the page named "Cuprum" does not exist. [04:12:44] This is usually caused by following an outdated history link to a page that has been deleted. Details can be found in the deletion log. [04:12:52] Yes, I know, I'll answer you in a bit [04:13:11] I didn't not see that [04:14:14] = MediaWiki 1.35 = [04:14:52] 1.35.0 or 1.35.1? [04:15:00] psql (PostgreSQL) 12.6 (Ubuntu 12.6-0ubuntu0.20.04.1) [04:15:19] Tell me how I can find the subversion and I'll tell you [04:15:27] although I don't think 1.35.1 fixes any postgres bugs [04:15:45] are you installing via package manager or via tarball downloaded from mediawiki.org? [04:15:46] oh nevermind it is in this file. its' 1.35.1 [04:15:52] k [04:16:15] tarball [04:16:30] i did try the package manager but it downloaded it to like /usr/share or something like that [04:16:52] so i just did the tarball and moved everything to /var/www [04:17:08] so the easiest thing would be to give up and use mariadb/mysql instead of postgres, but mediawiki sporadically failing to install on postgres is a bit concerning [04:18:05] Yeah, I couldn't even get mysql to work at ALL [04:18:29] But I am not concerned about installation since I *think* I know how to fix it [04:18:32] that sounds more like some setup/config issue [04:18:36] "sporadically" is way underselling it [04:18:47] this isnt a once in 20 times thing [04:18:57] What I'm more concerned about is the other issue [04:19:04] About no pages appearing [04:20:06] fwiw: mysql/mariadb is the primary supported database. postgres is... kinda... supported in that in theory the table schema and stuff is there and it all works fine, but you'll find it's completely unsupported in some popular extensions, and there's a handful of bugs with how mediawiki itself uses it too [04:21:00] I mean if I can't get this stuff to work with postsql then ill use mysql [04:21:25] I find postgresql to be frustrating to work with anyway (although I'm not good at databases as it is) [04:21:56] But I'm using vanilla ubuntu...there really shouldn't be any reason why I can't get either of the two database options to work correctly using the instructions [04:22:00] if you're aren't already tied to postgres for other things, I'd recommend using mysql or mariadb for mediawiki then [04:22:17] Well that's fantasitc, except that neither of those are cooperating either [04:22:35] I can't read minds, but if you report back with error messages I can perhaps help troubleshoot [04:22:52] well...shoudl I just throw out all I just did? [04:22:54] the most common cause of errors is simply lacking the PHP extension for it, you need mysqli installed for php for it to talk to the database [04:23:06] up to you! [04:23:31] can i just create another mediawiki directory [04:23:34] you'll probably find it less painful if you switch, especially if the old db doesn't have anything on it you need to save [04:23:35] will that work? [04:23:37] uh, sure? [04:23:49] I ask because I thought I trid that before, and it didnt work [04:24:01] you can even just rename LocalSettings.php to something else like LocalSettings.php.bak [04:24:10] and then the installer will prompt you to install again [04:26:00] Skizzerz: whenever i tried just doing that, it would just result in the site not loading properly [04:26:29] sounds like a webserver config issue then [04:27:17] No. It isn't [04:27:30] It's wikimedia saying the site is corrupted [04:27:40] or mediawiki, whatever its called [04:27:46] anyways [04:28:02] without a LocalSettings.php file, the wiki is treated as not installed. so i'm really not understanding what you are getting at here [04:28:19] When I put a folder into /var/www/html/wiki, it says "Forbidden, you don't have permission to access this resource." [04:28:32] Despite the fact that I moved it over with root [04:28:35] that would be a webserver config issue [04:28:42] Okay, you can't *know* that [04:28:47] this is vanille apache2 [04:28:49] your webserver is running as some user, e.g. apache [04:28:57] the files are owned by some other user (probably root in your case) [04:28:59] Why are you speaking with such authority about my system? [04:29:04] and probably marked as not world-readable [04:29:20] I did literally the same exact thing I did with the one that is currently working [04:29:25] because I've been doing this for years [04:29:41] Okay but I did literally hte same exact thing [04:29:41] file permissions issues are a very common cause of 403 Forbidden errors [04:29:48] Right, I know that, i discovered that yesterday [04:29:56] But I did literally the same exact thing [04:30:12] I extracted the file using file-roller in root [04:30:18] straight into /var/www [04:30:23] That worked perfectly yesterday [04:30:29] great, now chown them to apache or mark them world-readable [04:30:33] ill try it again just in case I did it wrong, but I dont know how I did it wrong [04:30:38] But I didnt chown them to apache [04:30:43] (might not be literally 'apache', may be 'www-data') [04:30:51] I didnt chown them to www-data either [04:31:47] https://dpaste.org/8mTD [04:31:59] do you know how many times ive tried installing this program? [04:32:09] the one "working" right now is mediawiki [04:32:12] I am attempting to be helpful here but you are making this very difficult. You mention an issue, I state a likely cause, your response is "it worked when I did it last time!" instead of investigating to see if that is indeed the issue so we can move on [04:32:15] the oneim trying atm is "wiki" [04:32:23] the permissions and owner, group, etc [04:32:34] Skizzerz: I just posted why though [04:32:43] drwx------ 14 root root 4.0K Feb 20 23:24 wiki [04:32:57] IS that not correct? And if it's not correct, then why does it work with the mediawiki one? [04:32:59] the wiki directory is owned by root and is not readable by other users [04:33:03] your webserver is NOT running as root [04:33:05] so it can't read the files [04:33:10] it is exactly the issue I stated it was [04:33:21] Okay, sure, but then why would it be running the *other* installation just fine? [04:33:31] I dont doubt what you say [04:33:50] no idea, check your apache config to see if it's still trying to read it from /usr/share instead of /var/www [04:35:14] alright, good tip [04:35:19] https://dpaste.org/D3e6 [04:35:22] i assume this is it? [04:35:32] it lists both /var/www and /usr/share [04:35:43] that's part of it, look at sites-enabled [04:36:07] you're looking for a block with a DocumentRoot inside of it [04:36:32] there is none. [04:36:42] the only mention of VirtualHost is in a comment [04:37:03] keep looking then, it'll be in there somewhere :) [04:37:05] oh, sorry, sites-enabled is the file [04:37:24] sites-enabled is a directory, inside of which will be one config file for each enabled website [04:37:40] https://dpaste.org/XaNe [04:37:48] right, yeah, i figured that out, sorry for my inaccuracy [04:38:31] but yeah this lists it as /var/www which is...what i was expecting since...that's what ive been working with the entire time [04:38:41] like that's the directory I did the fileupload through [04:38:42] looks like you have error logging configured, so you should be able to get more details from the apache error log [04:40:08] [Sat Feb 20 23:39:33.310078 2021] [core:error] [pid 81882] (13)Permission denied: [client 127.0.0.1:40410] AH00035: access to /wiki/index.htm denied (filesystem path '/var/www/html/wiki/index.htm') because search permissions are missing on a component of the path [04:40:59] yep, saying it's a file permissions issue [04:41:17] as to why your other site is working? I have no idea, but this confirms it's permissions [04:42:20] https://dpaste.org/8d9e [04:42:23] Yeah but they're all root. [04:43:50] There is no obvious reason I can tell at all why these two should have different behavior [04:44:06] I actually assumed at first that something about hte software *prevents* both from being run at the same time [04:44:12] nope [04:44:20] So how are these two different? [04:44:37] idk, I don't have access to your server to investigate, and I'm not particularly inclined to either [04:45:27] main takeaway is you know it's permissions-related, so fixing the permissions will fix that particular issue [04:45:59] is that changing the owner and group to everything int he directory to www-data? [04:46:48] most secure method would be changing group of everything to www-data and leaving owner alone (this prevents php from writing into any web-accessible areas, so you'd then need to chown images and other writable directories to www-data) [04:46:56] easiest would be chowning everything to www-data:www-data [04:47:27] up to you which you choose [04:48:32] okay, so that does work [04:48:47] but its so weird how the other directory is all root:root [04:49:03] what you said definitely makes sense, that it should be the webserver running it, not root [04:49:28] feel free to go down that rabbit hole if you wish, but I'm pretty stumped [04:50:26] it has to be some weird apache thing, i dont know [04:54:29] alright, thanks for the help...still getting the mysql error but im going to research it on my own for a while. certain to be a weird configuration issue on my end and likel yhas nothing at all to do with mediawiki [04:54:52] if youre curious the error is this: Cannot access the database: :real_connect(): (HY000/2002): No such file or directory. Check the host, username and password and try again. If using "localhost" as the database host, try using "127.0.0.1" instead (or vice versa). [04:54:59] but i dont expect any help here about that [04:57:23] if you're using "localhost" then it expects to be able to connect to a unix socket for mysql, e.g. /var/lib/mysql.sock [04:57:39] if you're using "127.0.0.1" it expects to connect over tcp port 3306 [04:57:47] ohh [04:58:11] do most people not install mediawiki on the same machine as the sql server? [04:58:28] most probably install it on the same server [04:59:28] check your mysql config to ensure whatever connection type you're trying to use is enabled. if you're using a unix socket, verify the path that mysql is creating it on and verify that the webserver has permissions to get there. If the permissions look right, check php.ini to see where php is expecting to find the socket file and verify they matc [04:59:30] *match [04:59:55] if you're doing tcp, ensure that networking is enabled in your mysql config [05:00:37] alright, all good leads. [05:00:46] I dont understand how mysql works at all so ill need to dig into ths [05:01:00] thansk for your help, again. sorry if i sounded a bit terse [13:32:07] Hiya. [13:32:45] How to read JSON file in Javascript? [13:47:22] $.getJSON() ? [13:47:30] https://api.jquery.com/jquery.getjson/ [14:42:09] I asked a q. earlier about a problem I was having running multiple instances of a Docker Compose setup for MediaWiki [14:43:26] It turns out the problem was due to my project layout being non-standard (with the docker-compose.yml file in a sub-folder named 'docker') resulting in namespace collision for the docker container names. [14:44:31] The solution was to use COMPOSE_PROJECT_NAME=sandbox2 in the .env file (with a separate value for each instance) [14:47:09] I'm now happily running 3 instances of my project on the same host, using the same codebase (docker-compose.yml) where each instance has their own APP, DB and ELASTICSEARCH containers. [15:45:20] freephile: where do you run your ocntainers? [23:10:53] Hello [23:11:50] !help I'm having a issue, a message of the abuse filter: "This action has been automatically identified as harmful, and therefore disallowed. If you believe your action was constructive, please inform an administrator of what you were trying to do. A brief description of the abuse rule which your action matched is: Block editing board descriptions [23:11:50] There are a lot of topics you could be asking about. Besides, this bot is mostly for experienced users to quickly answer common questions. Please just ask your question and wait patiently, as the best person to answer your question may be away for a few minutes or longer. If you're looking for help pages, we moved that to !helpfor. [23:11:50] for project and help pages" [23:12:39] I need help please [23:14:40] I need help, I can't edit board descriptions for project and help pages [23:15:38] !help [23:15:38] There are a lot of topics you could be asking about. Besides, this bot is mostly for experienced users to quickly answer common questions. Please just ask your question and wait patiently, as the best person to answer your question may be away for a few minutes or longer. If you're looking for help pages, we moved that to !helpfor. [23:16:05] !admin I need help, I can't edit board descriptions for project and help pages [23:16:05] To recreate the admin user, run "php maintenance/createAndPromote.php" on the command line. [23:21:52] !help I need help, I can't edit board descriptions for project and help pages [23:21:52] There are a lot of topics you could be asking about. Besides, this bot is mostly for experienced users to quickly answer common questions. Please just ask your question and wait patiently, as the best person to answer your question may be away for a few minutes or longer. If you're looking for help pages, we moved that to !helpfor. [23:21:56] This action has been automatically identified as harmful, and therefore disallowed. If you believe your action was constructive, please inform an administrator of what you were trying to do. A brief description of the abuse rule which your action matched is: Block editing board descriptions for project and help pages action has been automatically [23:21:57] identified as harmful, and therefore disallowed. If you believe your action was constructive, please inform an administrator of what you were trying to do. A brief description of the abuse rule which your action matched is: Block editing board descriptions for project and help pages [23:29:38] RodneyAraujo: is this on a Wikimedia project or an instillation of your own ? [23:32:04] Is on a Wikimedia project