[07:41:52] !help - seems like EventStreams is not working? [07:41:52] fuzheado: If you don't get a response in 15-30 minutes, please create a phabricator task -- https://phabricator.wikimedia.org/maniphest/task/edit/form/1/?projects=wmcs-team [09:28:17] fuzheado: sorry, I'm not familiar with that. Is that a tool or a cloudvps project or... other service offered by WMF? [09:28:45] * arturo searching wikitech [09:28:53] https://wikitech.wikimedia.org/wiki/EventStreams [09:30:07] I see [09:32:54] most of the WMF staff are sleeping right now (all in San Francisco) but we can report a bug in phab [10:40:12] fuzheado, that's something that runs in prod isn't it? [10:40:14] not cloud [10:40:28] I think that's true [10:41:46] * chicocvenancio waves to fuzheado [10:41:49] fuzheado, I would bring this up in -operations as well as filing a task [10:42:11] hi chicocvenancio [11:26:55] fuzheado: could you please open a phab task about the eventstream issue' [11:26:56] ? [11:28:09] ok [11:28:25] fuzheado does it work now? [11:29:01] seems to be now, yes, thanks [11:29:49] please still file it, because what I did didn't fixed anything, I only restarted it [11:30:19] ah ok [11:30:25] there maybe something wrong, I just did the "stop and start again" solution [11:30:39] so it may break again [11:34:16] filed - https://phabricator.wikimedia.org/T215013 [11:34:40] fuzheado: thanks! [12:04:55] !log account-creation-assistance VM instances accounts-appserver5, were stopped briefly due to issue in hypervisor (T215012) [12:04:58] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Account-creation-assistance/SAL [12:04:59] T215012: cloudvirt1015: server down - https://phabricator.wikimedia.org/T215012 [12:05:06] !log account-creation-assistance VM instances accounts-appserver5, were stopped briefly due to issue in hypervisor (T215012) [12:05:08] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Account-creation-assistance/SAL [12:05:14] !log deployment-prep VM instances deployment-deploy01,deployment-deploy02,deployment-fluorine02,deployment-kafka-jumbo-2,deployment-kafka-main-1,deployment-maps04,deployment-mcs01,deployment-mediawiki-09,deployment-memc04,deployment-ms-be03,deployment-ms-fe02,deployment-parsoid09,deployment-sca04,deployment-webperf12, were stopped briefly due to issue in hypervisor (T215012) [12:05:17] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Deployment-prep/SAL [12:05:26] !log hound VM instances hound-app-01, were stopped briefly due to issue in hypervisor (T215012) [12:05:28] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Hound/SAL [12:05:34] !log integration VM instances integration-slave-docker-1044,integration-slave-docker-1046,integration-slave-docker-1047, were stopped briefly due to issue in hypervisor (T215012) [12:05:36] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Integration/SAL [12:05:42] !log math VM instances drmf,drmf-beta,math-docker, were stopped briefly due to issue in hypervisor (T215012) [12:05:43] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Math/SAL [12:05:48] !log ores VM instances ores-puppetmaster-01,ores-sentinel-01, were stopped briefly due to issue in hypervisor (T215012) [12:05:50] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Ores/SAL [12:05:56] !log quotatest VM instances novaadminmadethis, were stopped briefly due to issue in hypervisor (T215012) [12:05:58] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Quotatest/SAL [12:06:05] !log rcm VM instances hafnium,neon,oxygen, were stopped briefly due to issue in hypervisor (T215012) [12:06:07] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Rcm/SAL [12:06:16] !log testlabs VM instances canary1015-01, were stopped briefly due to issue in hypervisor (T215012) [12:06:18] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Testlabs/SAL [12:06:24] !log thumbor VM instances packaging, were stopped briefly due to issue in hypervisor (T215012) [12:06:26] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Thumbor/SAL [12:06:33] !log twl VM instances twlight-prod,twlight-staging,twlight-tracker, were stopped briefly due to issue in hypervisor (T215012) [12:06:34] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Twl/SAL [12:06:40] !log video VM instances encoding02,encoding03, were stopped briefly due to issue in hypervisor (T215012) [12:06:42] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Video/SAL [12:06:51] !log webperf VM instances deployment-webperf12,ecmabot, were stopped briefly due to issue in hypervisor (T215012) [12:06:53] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Webperf/SAL [12:07:00] !log wikidata-dev VM instances wikidata-misc, were stopped briefly due to issue in hypervisor (T215012). [12:07:02] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Wikidata-dev/SAL [12:07:07] !log wikidata-query VM instances ldfclient-new, were stopped briefly due to issue in hypervisor (T215012) [12:07:09] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Wikidata-query/SAL [12:07:58] !log collection-alt-renderer VM instances mediawiki2latex, were stopped briefly due to issue in hypervisor (T215012) [12:07:59] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Collection-alt-renderer/SAL [12:44:14] !log admin T214012 depooling cloudvirt1015 and migrating all VMs to cloudvirt1024 [12:44:17] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Admin/SAL [12:44:18] T214012: Assign "suppressredirect" to rollbacker on newiki - https://phabricator.wikimedia.org/T214012 [12:44:29] !log admin T215012 depooling cloudvirt1015 and migrating all VMs to cloudvirt1024 [12:44:31] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Admin/SAL [12:44:32] T215012: cloudvirt1015: apparent hardware errors in CPU/Memory - https://phabricator.wikimedia.org/T215012 [18:31:37] VPS question... [18:31:47] I'm trying to set up a new server for the Dashboard [18:32:22] and instead of having my user be the one to own all the files and the deployment process, I want to create a new 'deploy' user that multiple people could log in as for the purpose of deploying the app. [18:32:51] Wes and I both have access to the server, and we created a new user 'deploy' within it. [18:33:19] But we can't figure out how we can log in as deploy via ssh (as opposed to logging in first and then doing `sudo su deploy`) [18:41:32] we've tried adding .ssh/authorized_keys (and rebooting afterwards) but that didn't do the trick. [19:33:12] ragesoss, that sounds like a bad idea [19:33:16] people should log in and sudo if you want to do that [19:33:38] I know how to allow external SSH in as a user that is not in your project's group, but I don't think it's a good idea to do that [19:34:00] Krenair: okay. we're trying to figure out a good way to do with via sudo. [19:34:23] ragesoss: why not use permissions on the group to do that? [19:34:41] I mean, do you have members of the project that you need to not have access to this? [19:35:19] no, but the way our current deploy configuration works is that the deploying user is the one who owns the Rails project... [19:35:40] right, and other users can't write to it [19:36:01] you could change the file permissions to allow the group to write to it [19:36:11] which is the way we've been running dashboard.wikiedu.org deployment all along, and makes it easy to give multiple people who need it the right to deploy and manage the deployed files. [19:36:16] you all should be member of the group, if I'm not mistaken [19:37:20] yeah just have the files be writeable by group and set the group to your project's group [19:37:30] ^this [19:37:43] that's similar to what we're working towards now. [19:37:46] which will be named something like project-$PROJECT [19:39:52] `chmod g+rw file` should allow all project members to work [19:40:22] or some variation of that to get the whole directory or execute permissions if needed [19:41:42] yeah, the part I was hoping to avoid is significantly rewriting the deployment config to account for there being multiple different users possibly doing the deployment. [19:42:24] (because the config needs to handle getting through the bastion proxy layer, so some things are currently hard-coded that wouldn't normally be with our deployment tool, Capistrano) [19:42:49] but that should all be solveable.