00:00:53 idk if you fixed it 00:00:56 you used to run 00:00:57 the vuln cgitr 00:01:01 that had bof 00:01:17 is the current cgit in repo vuln? 00:01:24 because according to git there are no updates 00:01:32 n because that mempodipper dude whitehatted it 00:05:18 loggy, pointer? 00:05:18 http://wire.cryto.net/logs/2013-02-07#T00-05-18 00:05:32 okay, day rollover works too 00:10:09 *** Anonymous_3102 (Anonymous_@cryto-5B79FCC0.hsd1.oh.comcast.net) has joined #crytocc 00:11:42 loggy, %d? 00:11:52 *** Anonymous_3102 has quit (User quit: Page closed) 00:12:33 haha 00:15:49 had to try 00:15:53 already had one bot vuln to this today 00:15:57 so I suppose nobody knows how to properly convert a mysql dump into a postgresql restore file? 00:16:10 its called sed awk and that one other thing 00:16:13 wait no 00:16:17 perl 00:16:22 thats the thing 00:16:23 use it 00:16:29 ryan: I can link you to the source 00:16:35 have you tried something very weird called a search on the internet? :P lol nah jsut kidding - I dont know sorry :P 00:16:38 actually, loggy can 00:16:42 loggy, help? 00:16:42 I'm a Python IRC logging bot. Source: http://inamidst.com/code/loggy.py Logging to: http://wire.cryto.net/logs/ 00:17:42 I searched already. nothing but vague bullshit as if people already know exactly how to do this manually. And all the scripts fail miserably. 00:17:56 wh1t3r4bb1t: what I am curious about 00:17:59 I don't like python but I don't think python likes utf8 00:18:04 8‹q"ŠË¶Âe1öVsæª…¬ðÈb»|i1þ>I[È] 00:18:05 !¡!£I*~iõ’§»d'qªL°2ƒ"Vk{Qˆð¬¦¾·‹öõ,g 00:18:05 à;©@6®Òu¸ø6ùCÜ£»ZT µAiñ.Ë+U6¨O"c¢ƒ6à‚¨®HbŽÕxìèç9°™aá+ý©xû§ý!úõš+¦Ým!37ä ÷Ú–<™‡úù¸{ôª•S(ÇÔ{&}N0·ÿ’M¢e&s÷`;h¤å®+h3%fŽx5¤o»„æž÷ 00:18:06 isn't SQL a more or less standard format? 00:18:20 yes it is 00:18:21 so couldn't you just import a mysql dump into postgre? 00:18:23 No 00:18:31 kind of 00:18:38 No 00:18:40 yes 00:18:48 Fuck you ryan 00:18:54 o omk 00:18:57 ok* 00:19:02 sigh 00:19:04 wh1t3r4bb1t, be nice 00:19:05 You are ignorant and as such going on the ignorant list 00:19:09 people are trying to help you here 00:19:24 what happened when you tried to import mysql dump into postgre? 00:19:37 No he's being ignorant 00:19:42 how so? 00:19:46 wh1t3r4bb1t: no, he's not 00:19:54 what happened when you tried to import mysql dump into postgre? 00:20:02 Ok, joepie91, I get an error saying that it is not a valid file 00:20:10 file..? 00:20:16 have you tried just running it as a query? 00:20:19 So I tried using a perl script I downloaded 00:20:24 a .sql dump is essentially a giant query 00:20:27 I... what 00:20:28 or multiple, actually 00:20:29 archive* 00:21:38 Yes but the SQL for mysql and postgre are different enough to cause incompatibility in the dump and restore 00:22:23 So I'm probably going to have to hand write the postgresql statements unless I can find a conversion tool that isn'y written half assed 00:22:44 you can probably just sed most of the queries to be compatible with postresql 00:22:57 or just make a script to convert it to some flatfile format you can easily convert to postresql 00:23:05 wh1t3r4bb1t: what in particular does it choke on? 00:23:10 if you run it as query, it should indicate around where it failed 00:23:32 NP: [Drivin' N' Cryin' - Chain Reaction] [Fly Me Courageous] [922kbps] DeaDBeeF 0.5.6-3jane 00:24:26 I even used the option --compatible=postgresql in my dump command 00:24:46 wh1t3r4bb1t: stupid question maybe, but have you tried without that flag? 00:24:50 just to see what happens 00:25:10 It's not choking on the conversion within the script but it's converting things to invalid postgre statements 00:25:23 Yes 00:25:30 tries it both ways 00:25:47 what error do you get when you import a non-postgresql-formatted .sql into postgresql, as a query, without any import tools? 00:25:56 I wonder 00:26:02 How are you importing that dump? 00:26:54 Well, I'm using pg_restore and I get this error: pg_restore: [archiver] input file does not appear to be a valid archive 00:27:34 ... have you *tried* running it as a query yet? 00:28:11 You mean with ececute? 00:28:16 execute* 00:28:43 thaaats expecting a targz or zip or so 00:28:43 No 00:29:03 hmmm 00:29:09 well, uh, running it with exec or so is kinda what they asked earlier 00:29:09 ok brb 00:29:21 that's what importing sql data is 00:33:12 NP: [Drivin' N' Cryin' - Let's Go Dancing] [Fly Me Courageous] [884kbps] DeaDBeeF 0.5.6-3jane 00:33:31 Tried it in a tar 00:33:40 errr from a tar 00:33:49 pg_restore: [tar archiver] could not find header for file toc.dat in tar archive 00:33:53 .. 00:33:59 wh1t3r4bb1t: just run it as a query 00:34:02 stop trying to use the restore thing 00:34:02 dude 00:34:03 ^ 00:34:04 fucking hell 00:34:08 really 00:34:11 you could've had this done 10 minutes ago 00:34:14 just run the thing as one giant query 00:34:33 (because that's what IT IS!_ 00:35:02 NP: [Dual Core - All The Things] [All The Things] [891kbps] DeaDBeeF 0.5.6-3jane 00:35:55 postresqlclientshit << three <'s? 00:37:36 s/< good point 00:37:55 I was wondering if there was some funky syntax in bash I was not aware of, haha 00:38:01 lady-3jane, I'm fucking tired and I don't need your cuntism 00:38:05 bash and perl remain hieroglyphs to me and probably always will be... 00:38:08 Shut the fuck up 00:38:14 wh1t3r4bb1t: I suggest you go to sleep and continue tomorrow 00:38:28 when you are so tired that you start shouting at everyone that's trying to help you, you probably really need sleep 00:38:35 <<< is just stdin 00:38:44 and it's more beneficial to the general atmosphere of the channel to continue when awake 00:38:48 wall<< ahh, cool 00:39:15 I was going to say "it's like cat"... wasn't far off :D 00:39:30 I'm fine. I just don't need people being asses 00:39:44 we're not, we've been nicer than previous times 00:39:46 I reckon only person here being an ass would be you 00:39:48 wh1t3r4bb1t: noone here is being an ass except for you, right now 00:40:06 somebody needs to go smoke a bowl >_> 00:40:13 I know I can run it as a query but I still need to convert the statements 00:40:13 as I said, what you need right now is sleep, not advice 00:41:05 No, I need to import this data. 00:41:10 And I will 00:41:31 put it in as one giant query, report back 00:41:40 *** drwoollynipples has quit (User quit: Leaving) 00:41:45 There ain't no rest for the wicked. 00:42:00 wh1t3r4bb1t: then I recommend you either follow the instructions given by various (helpful) users in this channel and keep back your nasty remarks, or try to get it fixed on your own 00:42:11 because I don't really get the idea that anyone here is enjoying your current mood/attitude 00:42:53 NP: [The White Stripes - The Hardest Button To Button] [Elephant] [820kbps] DeaDBeeF 0.5.6-3jane 00:43:56 Rewriting statements to work in postgre 00:44:27 Quick question... Has anyone here actually used postgre before, extensively? 00:44:55 not me, but how about you just try to import it *without* trying to rewrite things 00:45:02 1. export as mysql dump 00:45:07 2. run as query against postgresql 00:45:09 3. await results 00:45:11 4. ???? 00:45:14 5. boom or profit 00:45:22 go for the simplest attempt first 00:45:28 Because you can't do that. 00:45:36 wh1t3r4bb1t: have you tried it? 00:45:39 And that's lazy. 00:45:52 because I am running out of possible permutations to instruct you to JUST RUN THE DAMN THING. 00:45:57 and see what happens. 00:46:09 so, have you tried it or not? 00:46:28 Read about it like I have. No it won't work so stop arguing that. 00:46:42 I'd figure it might just work, since it's Standard Query Language 00:46:42 wh1t3r4bb1t: so no? 00:46:44 do it first 00:46:45 seriously 00:46:51 stop being stubborn and just run the damn query already 00:46:53 or structured? 00:46:53 shit 00:47:13 structured it is 00:47:16 lmao 00:47:23 Right do something that I read not to do from several sources... sure great idea. not. 00:47:37 wh1t3r4bb1t: JUST. FUCKING. DO. IT. ALREADY. 00:47:42 it's not going to blow up your fucking server 00:47:44 everything you read on the internet is truth 00:47:45 nor is it going to delete your dump 00:47:50 just fucking run the query 00:47:53 if it breaks you'll know in 10 seconds 00:47:59 and you can try something else 00:48:02 just run the goddamn thing already 00:48:04 I'll rud the statements once they are proper for postgre 00:48:18 okay, then I am not going to make any further attempts at helping you 00:48:22 it doesn't break it fucks up the database. 00:48:32 since you clearly have no interest of following the advice of those youa re asking for help 00:48:36 wh1t3r4bb1t: no, it fucking doesn't 00:48:46 if it doesn't work, it'll throw a fucking syntax error you idiot 00:48:50 that's how SQL engines are designed 00:49:45 either you try to run a standard mysql dump right now and report back the result, or this is the last thing I will say on this topic and you're on your own 00:49:52 your choice 00:50:14 grrr 01:11:08 wh1t3r4bb1t: he is right. SQL is transactional. If your THAT worried about damaging the database run the whole thing in a transaction and rollback at the very end, just so you can see how it goes 01:11:31 twitchyliquid64: be careful with that 01:11:38 myisam is most definitely *not* transactional 01:11:38 haha 01:11:47 im doing this @ command line 01:11:50 most engines do transactions, but SQL is definitely not transactional by default 01:11:57 wh1t3r4bb1t: that doesn't matter 01:11:59 brb food and attempts 01:12:05 its an engine feature 01:12:10 roger that 01:12:13 not a library feature 01:12:28 twitchyliquid64: actually I think InnoDB is the only mysql engine that does transactions 01:12:40 unfortunately 01:13:04 postgre is transactional 01:14:35 that's what I would have expected, yes, otherwise it probably wouldn't be used for financial transactions :P 01:14:40 it would worry me if it weren't 01:15:06 food make tummy happy 01:15:20 I suspect food also makes channel happy :P 01:15:23 even sqlite has transactions 01:15:32 ie: BEGIN, ROLLBACK, COMMIT 01:19:12 neat, I didn't know that's what transactional meant 01:19:18 loggy, pointer? 01:19:18 http://wire.cryto.net/logs/2013-02-07#T01-19-18 01:21:05 aaaahahahaha firefox apparently had crashing issues on facebook 01:21:13 that's part of what 18.0.2 is 01:21:14 LULZ 01:21:22 lol 01:21:25 loggy, rollover! 01:21:26 no, wait 01:21:32 that's ALL of what 18.0.2 is 01:21:35 wh1t3r4bb1t: you're doing it wrong 01:21:35 hahahahaha oh man 01:21:40 loggy, barrel roll! 01:21:44 :P 01:21:51 sad panda 01:22:02 :3 01:22:10 whiiich reminds me, when is ff19 due 01:22:24 I'm glad firefox has gone rapid release, it's getting better so much more quickly 01:22:34 loggy, find precious! 01:22:46 loggy:) DICKS 01:22:55 * joepie91 should mod loggy to make random asshole remark when highlighted with invalid command 01:22:58 :P 01:23:02 yes 01:23:07 absofuckinglutely 01:23:09 lady-3jane: it does not recognize :) 01:23:17 the more sarcastic the better 01:23:21 haha 01:23:23 I know, most people don't recognize it either 01:23:29 hahaha 01:23:40 I found it from someone in a chan... cause it's a smile! 01:23:51 lady-3jane: your nick suffix is beyond a turing-test 01:23:54 even humans fail to pass it! 01:24:13 ffuuuuuuuuu 01:24:29 humans must be fickle 01:24:45 they'd parse it aplomb if only it was prefixed by a space 01:25:10 oh, ff19 ships this month 01:25:18 coming to think of it, human mind isn't very well-calibrated 01:25:24 or maybe, too calibrated 01:25:50 it's fuzzy 01:26:08 wow, ff is removing xforms 01:26:16 xforms? 01:26:23 xml form schema 01:26:46 hahaha 01:26:46 lady-3jane: okay, is it important? 01:26:49 For the record statements made via the mysql dump will not work in postgresql 01:26:57 wh1t3r4bb1t: what does it break on? 01:27:16 I think it's not widely used or adopted by developers, so they're taking it out 01:27:20 Not only have I read this several time but I just tried it to make joepie91 happy. 01:27:30 w3c spec that failed the test of public opinion 01:27:34 the first line 01:27:43 wh1t3r4bb1t: yes, but with what error? 01:27:58 lady-3jane: I have a feeling all of w3c is starting to fail the test of public opinion, to be perfectly honest... 01:28:03 ERROR: syntax error at or near "`" 01:28:10 ... you have got to be kidding me 01:28:20 does postgresql not support backtick fieldname syntax? 01:28:25 I need to rewrite the statements as I told you a thousand times. 01:28:25 or is that a tablename? 01:28:42 So, now can I get some credit for being right and doing my homework? 01:28:57 yes 01:29:11 but I am really quite curious *why* it fails because I was under the impression that `` is standard syntax 01:29:13 joepie91:) to a certain degree I agree... but some of the times where groups are running against the spec are annoying... eg: microsofts competing webrtc clone 01:29:27 lady-3jane: the problem isn't with the specs, but with w3c 01:29:37 `` are standard for mysql 01:29:50 in postgre you need to use " 01:29:54 in an environment where a new platform can rise to massive proportions and die down entirely, all within 6 months, a 2-3 year period for discussing a spec is ridiculous 01:29:57 or double single quotes 01:30:03 wh1t3r4bb1t: for field/table names? 01:30:06 it's a pain in the ass 01:30:16 for any naming 01:30:20 what the hell 01:30:28 and even field contents 01:30:44 field contents is normal 01:30:46 it's called the double single quote escaping 01:30:57 or some shit like that 01:31:15 http://wiki.postgresql.org/wiki/Things_to_find_out_about_when_moving_from_MySQL_to_PostgreSQL 01:31:15 right 01:32:25 tried replacing all ` with "? 01:32:36 oh, in other words mysql sucks dick still 01:32:58 oh it's sunset 01:32:58 so eh, santrex, about that migration 01:32:59 ... 01:33:06 I still see fireball relinking every day 01:33:08 no wonder my screen is turning orange 01:33:11 so it's gotten significantly less stable 01:33:15 but still hasn't been migrated 01:33:17 wtf santrex 01:33:21 e.e 01:33:23 lady-3jane: heh 01:33:35 It's not the actual sunset, it's f.lux 01:33:54 http://stereopsis.com/flux/ 01:34:06 ofc 01:34:08 * joepie91 uses flux 01:34:17 just checkin 01:34:18 :) 01:34:29 I need to figure a proper night time color 01:34:44 pretty sure I need to set it to flourescent because of my overhead light 01:35:01 mmm 01:35:05 also, I should get back to work 01:35:12 finally have a functional hypervm setup 01:35:19 or well, as functional as hypervm gets in its intended state 01:35:30 (...) 01:36:30 joepie91, that... and this > http://www.postgresql.org/files/documentation/pdf/9.2/postgresql-9.2-A4.pdf 01:36:45 * joepie91 gives that URL the evil eye 01:36:46 pdf... 01:37:11 lol it's called a manual 01:37:13 my god 01:37:15 that's a fucking book 01:37:18 ._. 01:37:38 I'm sorry what? 01:37:40 2.6k pages? 01:37:45 I'll print and bind it when I gets me some more paper reams 01:37:49 two point six thousand pages? 01:37:53 really? 01:38:31 Yep. 01:38:42 I'm going to read the WHOLE thing. 01:38:48 Now. 01:39:17 I would not recommend that. 01:47:53 *** Anon_3102 (Anon_3102@cryto-5B79FCC0.hsd1.oh.comcast.net) has joined #crytocc 01:48:41 I got this 01:49:15 got what? 01:49:49 handled 01:56:32 wh1t3r4bb1t, have you tried http://pypi.python.org/pypi/py-mysql2pgsql 02:02:51 that sounds awesome 02:13:33 I'm only converting 5 empty tables and one populated table that has 17 entries so manually rewriting isn't so bad but for future referance that's a great link 02:14:29 I was just pissed off to find out that mysql is fucking retarded and used non-standard methods for EVERYTHING! 02:18:28 best way to force a system on people: make it proprietary 02:18:53 I always liked postgre just cause it was so "boring" in that regard 02:22:55 *** Akfreeworld has quit (Ping timeout) 02:29:57 wh1t3r4bb1t: I noticed that your mood greatly increased with food 02:30:05 you should eat more often :D 02:30:19 on a more serious note though 02:30:30 if one gets very grumpy when hungry, that's often an indication that one doesn't eat enough or varied enough 02:30:36 in my experience 02:31:50 I have a friend like that, but she's... got funky genetic issues lmao 02:32:12 She goes airheaded 15 minutes before she should eat, at the end of that 15m window she turns into a raging bitch 02:32:23 I learned quickly to indicate ahead of time that she needed food 02:32:23 :> 02:32:46 I think she likes being around me, because she's suddenly always fed when she needs to be :D 02:34:55 joepie91:) new chrome fixes pepper flash problem :) 02:38:25 lady-3jane: does she have diabeties? Because that flag goes up in my head when I hear that 02:43:20 twitchyliquid64, 02:43:33 yes AnonForecast_ 02:43:58 *** Professor_Xavier (5280cc2b@ProfessorXavier-10445.users.cryto) has joined #crytocc 02:44:01 were trying to get the relay bot running but were stuck on the VPS step 02:44:15 ok 02:44:23 whats wrong? 02:44:28 twitchyliquid64:) nah, she's just very broken 02:44:29 like, whats going wrong? 02:44:36 loootsa genetic problems 02:44:38 The server apparently not have ssh... 02:44:43 WTF 02:44:47 that's... worrying 02:44:48 to put it nicely 02:44:52 also 02:44:57 in case any of you missed it 02:45:01 this channel is now being publicly logged 02:45:04 ^ 02:45:11 prefix a message with [off] if you wish a message to be ignored by the public logbot 02:45:19 http://wire.cryto.net/logs 02:45:22 thats interesting 02:45:30 np, thanks joe 02:45:52 today is broken 02:45:57 I know 02:45:58 have to remove it 02:46:00 or something 02:46:00 * lady-3jane grins 02:46:05 the bot simply doesn't write a today.txt 02:46:09 Hi mom! 02:46:14 LOOK IM ON TV!!!! 02:46:26 lol 02:46:28 AnonForecast_: A server that doesnt have SSH or some form of shell is a shit server, and should be killed. 02:46:44 (unless headless and preconfigured) 02:47:15 The problem is that yesterday other guy put some things on the server, and today when I was to enter, the ssh port refused me. 02:47:30 Professor_Xavier: so it does have ssh 02:47:40 but the other guy 'bricked it'you have two options 02:47:41 Professor_Xavier: is it openvz? 02:47:49 I know, I think that a VPS MUST have ssh... 02:47:59 if you don't know, was it cheap for the amount of resources? 02:47:59 The owner of the server is AnonForecast_ 02:48:00 you can either use the VPS providers' shell thingy 02:48:02 if yes, it's probably openvz 02:48:08 or you can wipe it and do a fresh install 02:48:18 (the former is obviously preferable) 02:48:46 I believe the proper name of the former is 'serial console' 02:49:46 that depends 02:49:53 Idk... 02:49:56 technically speaking, a serial console is a physical device 02:50:12 you're usually either speaking of a 'shell dropper' (openvz) or VNC (KVM, Xen) 02:50:14 its virtualised 02:50:26 it still speaks the serial protocol 02:50:45 I... strongly doubt it 02:51:21 lmfao. 02:52:05 The other guy is afk (in theory)... 02:52:06 o.o 02:52:16 why cant SRN just revive? 02:52:33 *** AnonForecast_ is now known as AnonForecast 02:53:51 because DICKS 02:56:09 Its possible that the ssh daemon isn't running? 02:56:19 or changed the port 02:56:50 either port changed, or someone fucked up the iptables config 02:56:53 those are the most likely issues 02:57:06 such as trying to set up whitelisting and forgetting to whitelist port 22 02:57:28 Yep, I scanned the server with nmap but only showed me the '80' and '44088' 02:57:30 (happens.) 02:57:37 what's 44088? 02:58:02 TCP 02:59:04 omfg 02:59:23 er 03:00:00 I tried the 44088 port, apparently works. 03:01:15 there you go 03:02:21 Tnx! 03:03:29 OMFFFFFFFFG. Can't pase a fucking euro sign into the database commandline??? WTF??? 03:03:37 This is 2013 right? 03:04:00 your terminal 03:04:09 is probs in wrong mode 03:05:03 *** T0R_till (T0R_till@cryto-454686D9.compute-1.amazonaws.com) has joined #crytocc 03:05:35 Yep. 03:06:11