[17019] in athena10
Re: Postfix FQDN requested during installation
daemon@ATHENA.MIT.EDU (Anthony Grebe)
Mon Dec 2 08:54:49 2019
To: Benjamin Kaduk <kaduk@mit.edu>
CC: "Aaron M. Ucko" <amu@alum.mit.edu>, debathena <debathena@mit.edu>
From: Anthony Grebe <agrebe@mit.edu>
Message-ID: <73c44206-84da-d198-e042-459fd113739e@mit.edu>
Date: Mon, 2 Dec 2019 08:53:59 -0500
MIME-Version: 1.0
In-Reply-To: <20191202045834.GJ32847@mit.edu>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Thank you! It works now after
sudo service zhm start
renew
zwgc
zwrite agrebe
and the message goes through (to me).
I'll see if this persists over reboots or if I have to manually restart
zhm again.
Thank you for all your help here!
Best,
Anthony
On 12/1/19 11:58 PM, Benjamin Kaduk wrote:
> I suppose that we should try starting it manually to see what (if any)
> error messages it produces when it tries to start:
>
> sudo service zhm start
> <will prompt for sudo password>
>
> This content might also get preserved in /var/log/syslog, though I forget
> the precise details of what goes where.
>
> -Ben
>
> On Mon, Dec 02, 2019 at 04:45:51AM -0500, Anthony Grebe wrote:
>> Dear Ben,
>>
>> Yes, this is on my laptop, which is running Ubuntu 14.04. The command
>> results are
>>
>> agrebe@agrebe-laptop:~$ service zhm status
>> Usage: /etc/init.d/zhm {start|stop|restart|force-reload}
>> agrebe@agrebe-laptop:~$ pgrep zhm
>> [returns nothing]
>>
>> This is the case both before and after I run renew.
>>
>> Thank you,
>>
>> Anthony
>>
>> On 12/1/19 11:42 PM, Benjamin Kaduk wrote:
>>> Hi Anthony,
>>>
>>> Just to double-check, this is on your laptop running Ubuntu 14?
>>> If so, perhaps
>>>
>>> service zhm status
>>>
>>> would be useful.
>>>
>>> Also, how about
>>>
>>> pgrep zhm
>>>
>>> while we're at it?
>>>
>>> Thanks,
>>>
>>> Ben
>>>
>>> On Sun, Dec 01, 2019 at 10:24:41PM -0500, Anthony Grebe wrote:
>>>> Dear Aaron,
>>>>
>>>> Both variants give me the response
>>>>
>>>> initctl: Unknown job: zhm
>>>>
>>>> I've tried this before and after renew and got the same message.
>>>>
>>>> Thank you,
>>>> Anthony
>>>>
>>>> On 12/1/19 2:17 PM, Aaron M. Ucko wrote:
>>>>> Oops, please try
>>>>>
>>>>> initctl --system status zhm
>>>>>
>>>>> or (if you still get "command not found)
>>>>>
>>>>> /sbin/initctl --system status zhm
>>>>>
>>>>> NB: Most likely, exactly one of those two variants will work.
>>>>>
>>>>> Anyway, no need to apologize, and thanks for keeping the list copied.
>>>>>
>>>>> -- Aaron
>>>>>
>>>>> Anthony Grebe <agrebe@mit.edu> writes:
>>>>>
>>>>>> Dear Aaron,
>>>>>>
>>>>>> Thank you for explaining this, and I apologize that it's taken me so
>>>>>> long for me to respond.
>>>>>>
>>>>>> When I run "systemctl status zhm.service," I get the response
>>>>>> "systemctl: command not found." It's not super important to fix this,
>>>>>> so don't worry about trying to debug if this is a complicated problem,
>>>>>> although if this is something straightforward I can try to implement
>>>>>> it.
>>>>>>
>>>>>> Thank you,
>>>>>> Anthony
>>>>>>
>>>>>> On 11/7/19 3:40 PM, Aaron M. Ucko wrote:
>>>>>>> Thanks for clarifying!
>>>>>>>
>>>>>>> The difference between kinit and renew is that kinit is a standard
>>>>>>> Kerberos utility that only obtains raw Kerberos credentials, whereas
>>>>>>> renew is an Athena-specific alias that additionally authenticates to AFS
>>>>>>> (via the Athena-specific fsid -a, though standard aklog will typically
>>>>>>> also do) and tries to refresh your Zephyr service tickets.
>>>>>>>
>>>>>>> Speaking of Zephyr, what does "systemctl status zhm.service" report?
>>>>>>>
>>>>>>> -- Aaron
>>>>>>>
>>>>>>> Anthony Valenti Grebe <agrebe@mit.edu> writes:
>>>>>>>
>>>>>>>> Dear Ben,
>>>>>>>>
>>>>>>>> Thank you for your detailed response, and Im sorry that it took me so long to respond on my end.
>>>>>>>>
>>>>>>>> Ive tried answering both yes and no to the debathena-msmtp-mta prompt (on different install attempts), and it seems like Ive run into either prompts or
>>>>>>>> installation problems either way. But if this step isnt necessary for accessing AFS, then I guess I will just leave the FQDN as localhost.mit.edu and not
>>>>>>>> worry about this part.
>>>>>>>>
>>>>>>>> Ive tried to install debathena-standard from the installer script (that I got from debathena.mit.edu/install-debathena.sh) on both my laptop (running Ubuntu
>>>>>>>> 14) and my Chromebook (running Ubuntu 16 on top of Chrome OS; Im not exactly sure how this works other than that Ubuntu lives inside a chroot). In the past,
>>>>>>>> I hadnt been able to access AFS on my laptop, but for some reason it seemed to work today. (I think that Ive tried to run kinit before and still been
>>>>>>>> unable to access AFS; today I tried renew instead, so maybe that is the difference?) Given that it now seems to be working on my laptop, I would believe that
>>>>>>>> the Chromebook is having problems just because of conflicts between Ubuntu and Chrome OS.
>>>>>>>>
>>>>>>>> I cant seem to get Zephyr to work on either machine (it just says Hostmaster not responding while initializing Zephyr). This seems less important than AFS
>>>>>>>> access, though, given that Zephyr doesnt seem to be in as widespread use as in the past.
>>>>>>>>
>>>>>>>> The one question I have left: Is there a difference between kinit and renew, and what is the point of each? I would have naively thought that I would use
>>>>>>>> kinit to access AFS and only use renew if I had left my computer on for a long time, but empirically it seems like renew gives me access to AFS and kinit does
>>>>>>>> nothing discernible.
>>>>>>>>
>>>>>>>> Thank you,
>>>>>>>> Anthony
>>>>>>>>
>>>>>>>> On Oct 28, 2019, at 12:44 AM, Benjamin Kaduk <kaduk@mit.edu> wrote:
>>>>>>>>
>>>>>>>> Hi Anthony,
>>>>>>>>
>>>>>>>> There's a few points to cover here, so let me take them separately:
>>>>>>>>
>>>>>>>> This FQDN you're being asked for is part of the Postfix configuration, a
>>>>>>>> mail transfer agent; it's unlikely to affect your ability to use AFS and/or
>>>>>>>> zephyr. (Incidentally, my recollection is that most debathena systems
>>>>>>>> ended up with exim, not postfix, but I could be misremembering. I believe
>>>>>>>> there's also a question in the installer about debathena-msmtp-mta, for
>>>>>>>> which a "yes" answer would probably avoid the postfix question.)
>>>>>>>>
>>>>>>>> The "correct" FQDN value to use depends on where your machine is located
>>>>>>>> and who is providing the network for it. For example, machines in the
>>>>>>>> W20-575 athena cluster had hostnames like w20-575-3.mit.edu because IS&T
>>>>>>>> assigned them to be that way.
>>>>>>>>
>>>>>>>> Could you say a bit more about what procedure you're using to run the
>>>>>>>> installation? In particular, what "metapackage" (like debathena-login or
>>>>>>>> debathena-login-graphical) do you pick, and are you getting the installer
>>>>>>>> script itself from https://debathena.mit.edu/install-debathena.sh ?
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>>
>>>>>>>> Ben
>>>>>>>>
>>>>>>>> On Sat, Oct 26, 2019 at 12:02:24PM -0400, Anthony Valenti Grebe wrote:
>>>>>>>>
>>>>>>>> I'm trying to install debathena from the installer scripts online, but
>>>>>>>> during the installation, I'm asked to specify the fully qualified domain
>>>>>>>> name I want to use for Postfix and other programs. (The default option
>>>>>>>> appears to be "localhost.") What should I put here?
>>>>>>>> I've tried to run the installer several times without success (after
>>>>>>>> installation I'm never able to access my files in the AFS system or send
>>>>>>>> Zephyrs, even after typing renew or kinit), so presumably I'm doing
>>>>>>>> something wrong, which might have been guessing the wrong domain name to
>>>>>>>> use here.
>>>>>>>> Thank you for any help you can give me here.
>>>>>>>> Best,
>>>>>>>> Anthony
