Hi again,

> It actually shows an "Unexpected error". So, might it get 'stuck'
somewhere else?

I've found this in the logs (when clicking on the 'resend' button):

auth-server db mysql-1
{"Timestamp":1487849465049000000,"Logger":"fxa-auth-db-server","Type":"bin.server.summary","Severity":6,"Pid":20695,"EnvVersion":"2.0","Fields":{"code":200,"route":"getsessiontokenidverified","method":"GET","path":"/sessionToken/75e5939d18ec0d0294d695d8d4e3bc834d0039c938bc10e869c2cae7c8369601/verified","t":2}}
auth-server key server PORT 9000-2
{"Timestamp":1487849465058000000,"Logger":"fxa-auth-server","Type":"customs.check.1","Severity":2,"Pid":20700,"EnvVersion":"2.0","Fields":{"op":"customs.check.1","email":"[email protected]","action":"recoveryEmailResendCode","err":"EndpointError:
127.0.0.1:7000 error: connect ECONNREFUSED 127.0.0.1:7000"}}
auth-server key server PORT 9000-2
{"Timestamp":1487849465070000000,"Logger":"fxa-auth-server","Type":"mailer.send","Severity":6,"Pid":20700,"EnvVersion":"2.0","Fields":{"email":"[email protected]","op":"mailer.send","template":"verifyEmail"}}
auth-server key server PORT 9000-2
{"Timestamp":1487849465073000000,"Logger":"fxa-auth-server","Type":"mailer.send.1","Severity":2,"Pid":20700,"EnvVersion":"2.0","Fields":{"op":"mailer.send.1","err":"connect
ECONNREFUSED 127.0.0.1:25"}}
auth-server key server PORT 9000-2
{"Timestamp":1487849465082000000,"Logger":"fxa-auth-server","Type":"request.summary","Severity":2,"Pid":20700,"EnvVersion":"2.0","Fields":{"op":"request.summary","code":500,"errno":999,"rid":"1487849465046:tgmon-1.m-privacy.jua:20700:izi9j8pn:10174","path":"/v1/recovery_email/resend_code","lang":"de,en;q=0.5","agent":"Mozilla/5.0
(X11; Linux x86_64; rv:45.0) Gecko/20100101
Firefox/45.0","remoteAddressChain":"[\"10.90.0.13\",\"127.0.0.1\"]","t":35,"uid":"351f539135104c829024bcb905eea5a9","service":"sync","stack":"Error:
connect ECONNREFUSED 127.0.0.1:25\n    at Object.exports._errnoException
(util.js:870:11)\n    at exports._exceptionWithHostPort
(util.js:893:20)\n    at TCPConnectWrap.afterConnect [as oncomplete]
(net.js:1062:14)"}}

It seems to be trying to connect to a real mail. Could it be an
auth-server issue?

This is what the config for the auth-server looks like:

    {
      "name": "auth-server db mysql",
      "script": "bin/server.js",
      "cwd": "/usr/lib/fxa/fxa-auth-db-mysql",
      "env": {
        "NODE_ENV": "dev",
        "HOST": "0.0.0.0",
        "MYSQL_USER": "fxa",
        "MYSQL_PASSWORD": "superduperpassword",
        "MYSQL_SLAVE_USER": "fxa",
        "MYSQL_SLAVE_PASSWORD": "superduperpassword"
      },
      "max_restarts": "10",
      "min_uptime": "2m"
    },
    {
      "name": "auth-server key server PORT 9000",
      "script": "bin/key_server.js",
      "cwd": "/usr/lib/fxa/fxa-auth-server",
      "env": {
        "NODE_ENV": "dev",
        "IP_ADDRESS": "0.0.0.0",
        "SIGNIN_UNBLOCK_FORCED_EMAILS": "^block.*@restmail\\.net$",
        "PUBLIC_URL": "https://auth.mp.fxa";,
        "OAUTH_URL": "https://oauth.mp.fxa";,
        "CONTENT_SERVER_URL": "https://content.mp.fxa";
      },
      "max_restarts": "10",
      "min_uptime": "2m"
    },


Thanks!

Cheers,
Juanito

Am 23.02.2017 um 12:25 schrieb Juan Garcia:
> Hi Shane,
> 
> Thank you very much for that!
> 
> I definitely don't see any output from logs 0:
> 
> auth-server local mail helper-0 (out): mail_helper started...
> auth-server local mail helper-0 (out): mail_helper started...
> 
> [PM2] Streaming realtime logs for [0] process
> 
> This stays empty forever. In Firefox I do see an "A verification link
> has been sent to [email protected]" and the Firefox console doesn't show
> anything weird. Clicking on the "Didn't arrive?..." doesn't help. It
> actually shows an "Unexpected error". So, might it get 'stuck' somewhere
> else?
> 
> This is what my servers.json looks like:
> 
>     {
>       "name": "auth-server local mail helper",
>       "script": "test/mail_helper.js",
>       "cwd": "/usr/lib/fxa/fxa-auth-server",
>       "env": {
>         "NODE_ENV": "dev"
>       },
>       "max_restarts": "10",
>       "min_uptime": "2m"
>     },
> 
> Thanks again!
> 
> Cheers,
> Juanito
> 
> 
> 
> Am 23.02.2017 um 11:21 schrieb Shane Tomlinson:
>> Hi Juan, assuming you didn't change servers.json in fxa-local-dev, you
>> should be able to see verification links by typing:
>>
>>> ./pm2 logs 0
>>
>> 0 is the ID of the auth-mailer-helper, which displays the verification
>> links.
>>
>> Shane
>>
>>
>> On Thu, Feb 23, 2017 at 10:19 AM, Juan Garcia <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>>     Hi Vijay,
>>
>>     Thank you very much for your help!
>>
>>     > The links are still being logged as far as I can tell.
>>
>>     Weird. But good to know :)
>>
>>     > Node: v4.6.1
>>     > PM2: 1.1.3
>>
>>     I am using 4.3.1 (and unfortunately it won't be so easy to update that
>>     :( ) but the pm2 version is the same.
>>
>>
>>     Well, thank you very much anyway! I'm sure I'll find them at some point.
>>
>>     If not, I guess I'll just read the database. I would've liked to avoid
>>     this, but I looked yesterday in the db and the uid and code are pretty
>>     easy to read there.
>>
>>     Cheers,
>>     Juanito
>>
>>
>>     Am 22.02.2017 um 19:44 schrieb Vijay Budhram:
>>     > Hello Juan,
>>     >
>>     > The links are still being logged as far as I can tell. The auth-mailer
>>     > is the service that logs this message. When using `fxa-local-dev` and
>>     > using the `server.json` config you should be able to see it in the
>>     > console. A while back we did update the version of PM2, so that might 
>> be
>>     > some source of your troubles. A simple thing to try is updating PM2.
>>     >
>>     > These are the versions I run `fxa-local-dev` with that log verification
>>     > links.
>>     >
>>     > Node: v4.6.1
>>     > PM2: 1.1.3
>>     >
>>     > - Vijay
>>     >
>>     > On Mon, Feb 20, 2017 at 2:51 PM, Ryan Kelly <[email protected] 
>> <mailto:[email protected]>
>>     > <mailto:[email protected] <mailto:[email protected]>>> wrote:
>>     >
>>     >     These should still be getting logged, since I recall we use them 
>> when
>>     >     running in dev mode - FxA folks, can anyone shed some light on the
>>     >     below?
>>     >
>>     >       Ryan
>>     >
>>     >
>>     >     ---------- Forwarded message ----------
>>     >     From: Juan Garcia <[email protected] 
>> <mailto:[email protected]>
>>     <mailto:[email protected] <mailto:[email protected]>>>
>>     >     Date: 21 February 2017 at 01:07
>>     >     Subject: Verification and Confirmation Links (in logs)
>>     >     To: [email protected] <mailto:[email protected]>
>>     <mailto:[email protected] <mailto:[email protected]>>
>>     >
>>     >
>>     >     Hi again,
>>     >
>>     >     At some point, the account verification and device confirmation 
>> links
>>     >     used to be logged. I don't recall exactly which server use to give 
>> this
>>     >     information, but I could definitely see them with a ./pm2 logs.
>>     >
>>     >     And I could click on them in order to manually confirm the 
>> accounts (or
>>     >     in my case use the PyFxA in order to confirm automatically).
>>     >
>>     >     Does anybody whether I can get this logging back with some 
>> setting? Am I
>>     >     just missing something?
>>     >
>>     >     Thank you very much!!
>>     >
>>     >     Cheers,
>>     >     Juanito
>>     >
>>     >
>>     >     _______________________________________________
>>     >     Sync-dev mailing list
>>     >     [email protected] <mailto:[email protected]>
>>     <mailto:[email protected] <mailto:[email protected]>>
>>     >     https://mail.mozilla.org/listinfo/sync-dev
>>     <https://mail.mozilla.org/listinfo/sync-dev>
>>     >     <https://mail.mozilla.org/listinfo/sync-dev
>>     <https://mail.mozilla.org/listinfo/sync-dev>>
>>     >
>>     >     _______________________________________________
>>     >     Dev-fxacct mailing list
>>     >     [email protected] <mailto:[email protected]>
>>     <mailto:[email protected] <mailto:[email protected]>>
>>     >     https://mail.mozilla.org/listinfo/dev-fxacct
>>     <https://mail.mozilla.org/listinfo/dev-fxacct>
>>     >     <https://mail.mozilla.org/listinfo/dev-fxacct
>>     <https://mail.mozilla.org/listinfo/dev-fxacct>>
>>     >
>>     >
>>
>>     --
>>     m-privacy GmbH
>>     Werner-Voß-Damm 62
>>     12101 Berlin
>>     Fon: +49 30 24342334 <tel:%2B49%2030%2024342334>
>>     Fax: +49 30 99296856 <tel:%2B49%2030%2099296856> (NEU!)
>>     http://www.m-privacy.de
>>     GnuPG-Key-ID: 0x2DD3A649
>>
>>     Amtsgericht Charlottenburg, HRB 84946
>>     Geschäftsführer:
>>     Dipl.-Kfm. Holger Maczkowsky,
>>     Roman Maczkowsky
>>
>>
>>     _______________________________________________
>>     Dev-fxacct mailing list
>>     [email protected] <mailto:[email protected]>
>>     https://mail.mozilla.org/listinfo/dev-fxacct
>>     <https://mail.mozilla.org/listinfo/dev-fxacct>
>>
>>
> 
> 
> 
> _______________________________________________
> Dev-fxacct mailing list
> [email protected]
> https://mail.mozilla.org/listinfo/dev-fxacct
> 

-- 
m-privacy GmbH
Werner-Voß-Damm 62
12101 Berlin
Fon: +49 30 24342334
Fax: +49 30 99296856 (NEU!)
http://www.m-privacy.de
GnuPG-Key-ID: 0x2DD3A649

Amtsgericht Charlottenburg, HRB 84946
Geschäftsführer:
Dipl.-Kfm. Holger Maczkowsky,
Roman Maczkowsky

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Dev-fxacct mailing list
[email protected]
https://mail.mozilla.org/listinfo/dev-fxacct

Reply via email to